Exclude members from a dynamic calc - how ?

I've got a YTD figure as a dynamic calc in a 'YTD'member under the Time dimension. However users want to exclude certain members from the accounts dimension when the YTD dynamic figure is created.EGAccount dimension has members: Summary P&L Balance Sheet Want Balance Sheet not to be in YTD calcs.

Thanks for the advice.Did try this, and believe I've set it up correctly, but it's still creating a YTD figure for the Balance Sheet members.Time dimension has YTD fig, example member below: P3 YTD(2Pass,Dynamic calc)=P01+P02+P03Account dimension has below example members under Balance Sheet,which I've set to be 'Time Balance Last': Fixed Assets Stock Trade & Other Debtors Group Debtors Cash Trade Creditors What I want it to do for only P03 data to display for the Bal Sheet memebers.Have I missed something ?

Similar Messages

Storage option for Non leaf level dimension members: Store vs Dynamic calc

Hi All,
What is the general rule regarding the storage options for non leaf level members? My understanding is that it should be Dynamic Calc under normal circumstances and have it as store if we are going to load data at non leaf level. Is this correct? Are there any other considerations while defining the members?
Thanks and Regards,
Amol

Don't forget to consider whether the dimension is sparse or dense. Upper level dynamic calcs generally work well on dense dimensions as long as you aren't entering data into upper level members. Upper level dynamic calcs in a sparse dimension CAN work well, but usually only on smaller dimensions. This really depends on what else you have going on in your cube. On large sparse dimensions, upper levels are almost always stored, but this is one of those areas where you can sometimes bend the rules.
Also, don't forget to consider the calc order implications of making something stored or dynamic.
- Jake

Excluding Members from EPMA application - performance issues?

We are building a new application using dimensions from our Shared Library and I had a question about excluding some members.
For one dimension, I was able to use the "Add to App View" functionality, which was able to bring in only the one tree of members I wanted, without having to exclude anything, which seems to be the best way of doing this.
For another dimension, I need to pick and choose members from within the hierarchy, so I will need to add almost all parents, and then go through and exclude some members. Will this cause any performance issues having excluded members? Will the excluded members get deployed to planning or do they just sit in EPMA?
Any help would be appreciated.

Hi,
Excluded members are not deployed to Planning, therefore would not impact performance negatively.
Cheers,
Alp

Excluding members from calculation

I am trying to get this calculation to not include 2001 & 2002 members from the time dimension. I have tried adding this to the IF statements:AND (@CURRMBR(TIME) <> (@IDESCENDANTS(YR2001))) AND (@CURRMBR(TIME) <> (@IDESCENDANTS(YR2002))))It's not working. Please Help me.FIX(&CURRDAY, @UDA(TIME, "LastDay"), @UDA(TIME, "HistMthEnd"), @LEVMBRS(Entity, 0), @LEVMBRS(Accounts, 0)) ACTYTD_LOAD( IF ((@CURRMBR(TIME) <> #MISSING) AND (@ISUDA(TIME, "HistMthEnd"))) @ANCEST(TIME,3) = @CURRMBR(TIME); @ANCEST(TIME,2) = @CURRMBR(TIME); ELSEIF (@ISUDA(TIME, "HistMthEnd")) @ANCEST(TIME,3) = #MISSING; @ANCEST(TIME,2) = #MISSING; ELSEIF ((@CURRMBR(TIME) <> #MISSING) AND (@ISUDA(TIME, "LastDay")) AND (NOT (@ISISIBLING(&CURRDAY)))) @ANCEST(TIME, 4) = @CURRMBR(TIME); @ANCEST(TIME,3) = @CURRMBR(TIME); @ANCEST(TIME,2) = @CURRMBR(TIME); ELSEIF ((@ISUDA(TIME, "LastDay")) AND (NOT (@ISISIBLING(&CURRDAY)))) @ANCEST(TIME, 4) = #MISSING; @ANCEST(TIME,3) = #MISSING; @ANCEST(TIME,2) = #MISSING; ELSEIF ((@CURRMBR(TIME) <> #MISSING) AND (@ISMBR(&CURRDAY))) @ANCEST(TIME, 4) = @CURRMBR(TIME); @ANCEST(TIME,3) = @CURRMBR(TIME); @ANCEST(TIME,2) = @CURRMBR(TIME); ELSEIF (@ISMBR(&CURRDAY)) @ANCEST(TIME, 4) = #MISSING; @ANCEST(TIME,3) = #MISSING; @ANCEST(TIME,2) = #MISSING; ENDIF);

Could This Work ?/****************************//* Set &CurYear == "YR2003" *//****************************/If(@IsMbr(&CurYear)) {Your Code Here }else/* do nothing */endif;/* refactored but then maybe not */If (@curMbr("TIME") <> #Missing) then If (@isUda("TIME","HistMthEnd") then @ANCEST(TIME,3) = @CURRMBR(TIME); @ANCEST(TIME,2) = @CURRMBR(TIME); Else If (@isUda("TIME","LastDay") then If (NOT (@IsSib(&CurDay)) then @ANCEST(TIME,4) = @CURRMBR(TIME); @ANCEST(TIME,3) = @CURRMBR(TIME); @ANCEST(TIME,2) = @CURRMBR(TIME); Endif; Else If (@IsMbr(&CurDay)) then @ANCEST(TIME,4) = @CURRMBR(TIME); @ANCEST(TIME,3) = @CURRMBR(TIME); @ANCEST(TIME,2) = @CURRMBR(TIME); Endif; Endif; Endif;Else If(@isUda("TIME","HistMthEnd") then @ANCEST(TIME,3) = #MISSING; @ANCEST(TIME,2) = #MISSING; Else If (@isUda("TIME","LastDay") then If (NOT (@IsSib(&CurDay)) then @ANCEST(TIME,4) = #MISSING; @ANCEST(TIME,3) = #MISSING; @ANCEST(TIME,2) = #MISSING; Endif; Else If (@IsMbr(&CurDay)) then @ANCEST(TIME,4) = #MISSING; @ANCEST(TIME,3) = #MISSING; @ANCEST(TIME,2) = #MISSING; Endif; Endif; Endif;Endif;

Exclude members from a scope - MDX SSAS

Hi all,
I'm just beginning with MDX so the answer may be obvious...
I'm trying to do a currency conversion with an MDX statement in my Cube SSAS 2012.
Here is my script :
SCOPE( LEAVES([Entity]) );
SCOPE( LEAVES([Time]) );
SCOPE( LEAVES([Currency]));
SCOPE( [Account].[Account].[Total ACCOUNT].members)
THIS = ([Measures].[Value],[Currency].[Currency].[Local])*([Measures].[Value],[Account].[Account].[Fx Rate]);
END SCOPE;
END SCOPE;
END SCOPE;
END SCOPE;
The problem is I want to exclude frome the scope Currency my local Currency in order to make the conversion only if a currency (€,$, £) is selected.
I tried the following syntax but it always return a "MDX script is not valid" :
SCOPE( LEAVES([Currency], Except (LEAVES([Currency],[Currency].[Currency].[Local]);
SCOPE( [Measures].[Value] , Except ([Currency].[Currency].members,[Currency].[Currency].[Local]);
SCOPE( [Measures].[Value] , Except (LEAVES([Currency],[Currency].[Currency].[Local]);
SCOPE( LEAVES([Currency] - [Currency].[Currency].[Local]);
Could you please help me with this ? Thanks.

Hi MNelane,
Please try to use the following MDX command:
Scope( Leaves([Date]) , Except([Currency].[Currency].Members, [Currency].[Currency].[Local));
For more information about currency conversion in SQL Serve Analysis Services, please refer to the articles below:
Currency Conversion in SSAS 2012:
http://social.technet.microsoft.com/wiki/contents/articles/18672.currency-conversion-in-ssas-2012-multidimensional-tabular.aspx
Currency Conversion in Analysis Services:
http://consultingblogs.emc.com/christianwade/archive/2006/08/24/Currency-Conversion-in-Analysis-Services-2005.aspx
Regards,
Elvis Long
TechNet Community Support

Dense dim - dynamic calc

Hi
Essbase / Planning 11.1.2.1 - BSO db.
We are reviewing our app / db design following implementation last year. One of the things I have noticed is that one particular dense dimension has all members as stored (ie the non-level 0 members are not dynamic calc). Dimension has no member formulas, it is a straight roll up with consolidation for members consisting of (+ and ~).
I have changed this in our dev environment and ran some tests - calc time dramatically improved and total page file size halved (hard disk space becoming a slight issue for us so this is useful).
If we ran with this change, is there anything we need to do or be aware of, other than amending any business rules to exclude calc dims or partial aggs on the amended dimension? It seems a fairly low risk change, but looking for clarification that this is the case.....
The documentation on this states that any required combinations at non level 0 members will be calculated on the fly (eg a user retrieve). Is the same true if a non level 0 intersection is used within a business rule? (testing this on Sample Basic seems fine, again just looking for confirmation).
Thanks
JB

Yes, the same is true within a rule (i.e. if you reference an upper level in a dense dimension, Essbase will calculate it for you).
I think the only major functional issue that you haven't mentioned is that you need to be sure that none of your existing loads / calculations / user lock & send activities depend on being able to store a value at an upper level - for example, that you never load to a Quarter and then run a calc that allocates down to the Periods.

Data not replicated with partition and dynamic calc

HI
I am using Essbase 11.1.2.1.
I want to use a replicated pratition wetween two Essbase BSO applications.
But in my source application, I have to send an account ACCOUNT (level 1) with several stored members and 1 dynamic calc member with formula. Due to this Dynamic calc account, the partition doesn't work (data are not replicated).
How could I do?
Thanks
Fanny

You're right, dynamic calc account are not issues. I am using them in partition.
But py issue is there :
The source dimension is like this :
TAX (Dynamic Calc)
- 6xxxxxxx
- 6yyyyyyy
- 6zzzzzzz (Dynamic Calc) = formula
The target dimension is like this :
TAX
And so I need to send TAX (Source) to TAX (cible).
I don't think it is possible, but I would like a confirmation before using something else.
I hope it is clearer now.
thanks
Fanny

Input data into dynamic calc in Planning forms

Hi guys,
Have someone tried to combine these two requirements:
1. to have upper level members dynamic calc
2. to give users the ability to input data into those upper level members through Planning forms.
I need to do that in order to pass inputted values into HBR, and allocate those values to the leaf level across multiple dimensions. I need those members dynamic calc because otherwise I would need to aggregate data across 7 dimensions and that takes too long. Those allocations are suposed to happen constantly and are the main purpose of application.
I know you can have dummy stored members that correspond the uper level dynamic members, but then the user will have input forms without current data and will be required to check reports/forms with dynamic calc members prior to updating data.
I wonder if it is a realistic task to change jsp files that generate those forms, so that data can be inputed into the form, but instead of passing it to Essbase cube to send it to relational database.
P.S.
This is related to the thread I opened about optimizing recalculation time:
Recalculatiion takes much longer than initial calculation
I received a lot of valuable advices that would definitely work in other situations, but in my case they seem to contradict either user concurrent access or performance requirements.
Thanks a lot!
Dmitry

Hi Glenn,
I think i found a workaround for this, or may be i am missing something. I will replicate my hierarchies so that one hierarchy will have uper level stored members, and another dynamic calc. Once user loads the form it will run on-load script that will copy data from corresponding dynamic calc to stored slice. The updated data will be alocated to the leaf level, but will never be aggregated. Since reporting is done from ASO cube i only care about the leaf level and current selection in the form.
Thanks!

Datacopy of dynamically calc'd data

In Essbase 6.5, I am looking to copy data in an ACCOUNTS dimension from one dynamically calc'd member to a level zero member but it doesn't work. Any ideas?

The last 2 queries are getting optional data out of the DB. The user is not required to fill out those fields but if they do, I want to get that data.
I have designed it this way following the instruction of the book "head first php and my SQL" by Head First Labs. It said that you should minimize duplicate data in a table as much as possible to keep them small. Instead put the data in a separate table and reference it with a key. Your tables should only describe one specific thing, so thats what I did. I have them linked with foreign keys and primary keys.
In my case each user can have a vehicle saved for them, maybe 2 or 3. for each vehicle they have the option of listing a car audio setup for that vehicle. Now when they change their setup and update it on the site, a new setup entry is made. That way the old pics/video of their old setup are still correct and all new pics will be correct as well. So essentially each vehicle can have maybe 5. 10 setups linked to it. Hence the separate table for video data, vehicle and setup. make sense?
As for the joins, I was kind of confused on how to do it correctly with my particular queries. And since the 2nd and 3rd queries dont always need to be executed, i thought if i left it as 3 it might save some execution time as only 1 short query needs to be executed.
what is your opinion on the matter?
and what do you mean by procedural language? like if/else?

Substitution variable in Dynamic Calc

Hi,
We are using Essbase 9.3.0 on Windows and are seeing this behavior in our BSO cubes.
When we use a substitution variable in a Scenario member with Dynamic Calc (not store) setting, after the first retrieve, if we change the value of the substitution variable, the subsequent retrieves do not generate updated results.
I suspect that the value is cached in the Dynamic Calculator Cache, and for some reason does not track changes in Substitution Variables to know that the value must be re-calculated. Here is what I see in the Application log -
[Mon Aug 09 10:31:51 2010]Local/App1/db1/user1/Info(1020055)
Spreadsheet Extractor Elapsed Time : [0.032] seconds
[Mon Aug 09 10:31:51 2010]Local/App1/db1/user1/Info(1020082)
Spreadsheet Extractor Big Block Allocs -- Dyn.Calc.Cache : [4] non-Dyn.Calc.Cache : [0]
This says that 4 blocks were used from the Dynamic Calc Cache, and none from outside it. Does this mean that existing blocks were read and not re-populated?
If I make a change to the formula, wherein I hard code the value of the sub var and perform the retrieve, then the value is updated. Subsequent retrieves, after restoring the formula still returns the updated results.
My question is, is this expected behavior? Or am I doing something /reading something wrong?
Thanks,
Andy

when a subst variable value is changed... to use the value in member formula or calc script, the concerned application has to be restarted...
- Krish

Dynamic Calc referencing another Dynamic Calc

Hi,
I found a problem today in a Dynamic Calc member formula.
Member A has in formula: B;
Member B has in formula: C + D;
Both members are Dynamic Calc and while member B shows the correct result, member A shows nothing in forms. If I switch the formula of member A to C + D; then it shows results.
Is there any problem of Dynamic Calc members referencing another Dynamic Calc members?
Thank you

or change the position of member A/member B in the outline.^^^Exactly, Essbase is calculating the dimension top to bottom and if A needs B, it needs to be after B or as Andre stated, you need to stick a two-pass on A. I prefer not to use two-pass unless i need to as it can FUBAR my YTD and variance calcs. It's just easier to have it work in the "right" order.
Regards,
Cameron Lackpour

How to add dynamic calc storage property in planning?

hii am having problem in adding dynamic storage property inplanning application.i am using HAL to load members (metadata) into planningapplication i have all non level o members as dynamic calc. when irun HAL 3/4th of records are rejected.can anyone tell how to add dynamic calc property to mymembers. thanks and regards,Balu

Hi Ritu,
It's not difficult once you know how.
1) Go to: System Administration -> System Configuration -> Knowledge Management -> Content Management -> User Interface -> Search -> Search Option Set
2) Edit UISearch
3) Select your custom property from the list beside the option 'Allowed Predefined Properties' and hit save.
On 'Advanced Search' your property should now be listed under 'Filter by Predefined Properties'.
You may also add it to 'Allowed Sort Properties' if you like.
I hope this helps,
Patrick.

Problem with Dynamic Calc members in calc script

Hi
i wrote a calc script which calculates the value of acct2 which is dependant on the value of acct1 that is calculated from acct0 as bellow:
FIX(
M1
acct1(
acct1=acct0->M2;
acct2=acct1->M2;
ENDFIX
the value of the intersection of M1->acct0 is 100 as input ,what i wanted from this calc script is the acct2->M1 to be 100 after executing the script once
but the fact is i have to run it twice to get the expected result.
the outline is like this:
M:
M2 Dynamic calc M2=M0+M1
M0 Stored
m1 stored
Account:
acct0 stored
acct1 stored
acct2 stored
Can anyone tell me the reason and how to solve it?
Edited by: user10450070 on 2011-1-25 上午1:38

Is acct1 correct after one run of the calculation, but acct2 incorrect? If so, it's because Essbase is calculating them both at the same time (parallel), whereas it has to be forced to calculate acct1 first and acct2 second. You can do this with separate fixes as below:
FIX(M1)
acct1=acct0->M2;
ENDFIX
FIX(M2)
acct2=acct1->M2;
ENDFIX
Or, you can you can force it into calculating in serial mode:
SET CALCPARALLEL 0;
FIX(M1)
acct1=acct0->M2;
acct2=acct1->M2;
ENDFIX
Sabrina
Edited by: SabrinaD on Jan 26, 2011 7:56 AM

Shared members and dynamic calc

I am trying to replicate a new cube from current GL cube and wish to remove unused shared members if they have any impact on essbase.
2/3 of my accounts (dense) member is stored with the remainder being shared members. Shared members do not add to block size. But having so many of them, does it impact on calc scripts or retrievals or any other impacts?
Secondly, in accounts and divisions, we have four levels. except for level 0, the remaining levels are all dynamic calc. Division is sparse member. Its not advisable to have dynamic calc on dense dimension. What about sparse dimension like division? Will it be better to change level 2&3 to dynamic and change level 1 to store as well?
We have also been advised by our consultant to change accounts to sparse dimension considering the number of times we need to update outline for new members (stored and shared).
Dimension          Type          Stored     Shared
Measure               Dense     1378     796     rest
Time               Dense     106     13     rest
Year               Dense     9     8
Currency          Sparse     12     9
Scenario          Sparse     41     38
Market               Sparse     20     12
Division          Sparse     490     302     rest
Product               Sparse     635     308
Reportcode          Sparse     327     299

Hi,
Having shared members in dense hierarchy will not have much of impact on Cube size or retrieval performance.
but its always advisable to avoid unnecessary hierarchies (shared or stored or dynamic).
Having top level dense members as dynamic lines is a good design but having sparse dynamic calc will impact retrieval performance.
its not at all advisable to make sparse members as dynamic calc but if needed we can make sparse members with very few children as dynamic calc (or dynamic calc & store). yet again its not advisable to have a dynamic calc children to a sparse stored parent as this will affect the batch calculation while aggregating parent sparse member.
And as suggested by your consultant it is feasible to make the dimension getting modified more often, as a sparse dimension as this will reduce the restructuring time (sparse restructure will take less time compared to dens restructure).
But that alone cannot be considered as factor as there are many other factors to be considered for making a dimension sparse.
- Krish

Retrieval performance become poor with dynamic calc members with formulas

We are facing the retrieval performance issue on our partititon cube.
It was fine before applying the member formulas for 4 of measures and made them dynamic calc.
The retrieval time has increased from 1sec to 5 sec.
Here is the main formula on a member, and all these members are dynamic calc (having member formula)
IF (@ISCHILD ("YTD"))
IF (@ISMBR("JAN_YTD") AND @ISMBR ("Normalised"))
"Run Rate" =
(@AVG(SKIPNONE, @LIST (@CURRMBR ("Year")->"JAN_MTD",
@RANGE (@SHIFT(@CURRMBR ("Year"),-1, @LEVMBRS ("Year", 0)), @LIST("NOV_MTD","DEC_MTD")))) *
@COUNT(SKIPNONE,@RSIBLINGS(@CURRMBR ("Period")))) + "04";
ELSE
IF (@ISMBR("FEB_YTD") AND @ISMBR ("Normalised"))
"Run Rate" =
(@AVG (SKIPNONE, @RANGE (@SHIFT(@CURRMBR ("Year"),-1, @LEVMBRS ("Year", 0)),"DEC_MTD"),
@RANGE (@CURRMBR ("Year"), @LIST ("JAN_MTD", "FEB_MTD"))) *
@COUNT(SKIPNONE,@RSIBLINGS(@CURRMBR ("Period")))) + "04";
ELSE
"Run Rate"
=(@AVGRANGE(SKIPNONE,"Normalised Amount",@CURRMBRRANGE("Period",LEV,0,-14,-12))*
@COUNT(SKIPNONE,@RSIBLINGS(@CURRMBR ("Period"))))
+ "Normalised"->"04";
ENDIF;
ENDIF;
ELSE 0;
ENDIF
Period is dense
Year is dense
Measures (normalised) is dense
remaining all sparse
block size 112k
index cache to 10mb
Rertrieval buffer 70kb
dynamiccalccahe max set to 200mb
Please not that, this is partition cube, retriving data from 2 ASO, 1 BSO underline cubes.

I received the following from Hyperion. I had the customer add the following line to their essbase.cfg file and it increased their performance of Analyzer retrieval from 30 seconds to 0.4 seconds. CalcReuseDynCalcBlocks FALSE This is an undocumented setting (will be documented in Essbase v6.2.3). Here is a brief explanation of this setting from development: This setting is used to turn off a method of reusing dynamically calculated values during retrievals. The method is turned on by default and can speed up retrievals when it involves a large number of dynamically calculated blocks that are each required to compute several other blocks. This may happen when there is a big hierarchy of sparse dynamic calc members. However, a large dynamic calculator cache size or a large value of CALCLOCKBLOCK may adversely affect the retrieval performance when this method is used. In such cases, the method should be turned off by setting CalcReuseDynCalcBlocks to FALSE in the essbase.cfg file. Only retrievals are affected by this setting.

Exclude members from a dynamic calc - how ?

Similar Messages

Maybe you are looking for