Formula member to sum based on a model

Similar Questions

• Question - formula Member

  Based on past requirements for 'Suffering' (a member dynamic calc) is the formula of Member
  
  Suffering = before year-> year Total + @SUM (& CurrYear->(Jan:&Priormonth));
  
  The logic above will work well from next month, i.e. February, but fails to work when the current month is the month of January.The problem now is that & Priormonth = decrease, so the formula is the addition of Jan: Dec values for the current year, which shouldn't be the case. For the current month, i.e. January suffering should just be the total value of the previous year. How this formula member could be changed in a way that it satifies irrrespective requirements of which it is?
  
  I can change to -.
  
  Suffering = & title-> YearTotal + @SUM (& CurrYear->(Jan:&Currmonth)) - & Currmonth;
  
  Please let me know.
  Thank you.

  A very quick thinking would be to consider applying if conditional. OR | ON THE OTHER. ELSEIF | ENDIF logic.

  Thank you

  Todd Rebner

• Preload an image in a page based on a model

  I have a fairly simple problem here, there must be a simple solution. I hope!
  
  I have a site whose pages are all based on a model of DW. On each page, there is only one image (a different on every page) I want to have preload. It is not part of all bearings but is an important graphic element and it's distracting that it is the last to load each time. All I want to do is add to the list of prestressing in each page of the < body > tag, but I am unable to do so is not an editable region. I tried to go in the model and the addition of an editable region or as an option within the < body > tag, but it doesn't let me do and inserts it after the tag.
  
  I don't want to loose my pages of the template, I'm sure that the customer will have to future changes - the scale of the site.
  
  How can I do this? Thanks in advance for any help.
  
  

  > I tried to go in the
  > model and adding an editable or optional region to the breast of theTag, but
  > it doesn't let me do and inserts it after the tag.

  the editable regions cannot contain the head or body tag.

  Select the body tag in the quick tag selector (left margin of the lower part of the design
  window)

  then go on change--> models--> add editable attribute
  and add an onload attribute.

  in the page of the child, use edit-> model parameters to add the preload.

  Use or some other preloader javascript inside an editable region in the
  Head section.

  --
  Alan
  Adobe Community Expert, dreamweaver

  http://www.Adobe.com/communities/experts/

• ASO - formula Member MDX

  Dear,

  In my current requirement that I have cam across, I applied under the formula of dynamic dimension ASO member.

  VC_YTD--(SOMME (PeriodsToDate ([période].))) Generations (2) [period]. CurrentMember), [see]. [VariableCost]))

  FC_YTD - (SUM (PeriodsToDate ([period].)) Generations (2) [period]. CurrentMember), [see]. [FixedCost]))

  FixedCost - SUM ({DESCENDANTS ([Custom1]. (CURRENTMEMBER,10,LEAVES)}, [FC_FIS])

  VariableCost - SUM ({DESCENDANTS ([Custom1]. (CURRENTMEMBER,10,LEAVES)}, [VC_FIS])

  FC_FIS - SUM ({DESCENDANTS ([Custom1]. (CURRENTMEMBER,10,LEAVES)}, [VC_FIS])

  
  VC_FIS-

  CASE WHEN IsLevel ([account]. CurrentMember, 0) THEN

  IIf (IsAncestor ([A_4000000], [account]. (CurrentMember), (([MTD] * ([BegBalance], [NoLocation], [NoCostCenter], [NoProduct], [UserInput], [Budget], [approuvé], [Local], [aucune Entity],[FY14],[MTD])) / 100), 0)

  on the other

  SUM ({DESCENDANTS ([account]. (CURRENTMEMBER,10,LEAVES)}, [FC_FIS])

  End

  I know this isn't the right way but due to requiremnet I do the same thing.

  Now when I retriev the Member in excel my excel is dying upward and it gives no result.

  In the newspapers, I get below error-

  [FixedCost] member formula is complex. If possible, add a non-empty directive for scattered data optimization.

  The Member [VariableCost] is complex. If possible, add a non-empty directive for scattered data optimization.

  The Member [VC_FIS] is complex. If possible, add a non-empty directive for scattered data optimization.

  Can you suggest me to this.

  Thank you.

  try using NONEMPTYSUBSET()

  "This can help to optimize the queries based on a wide range for which all non-empty combinations is known to be small. NonEmptySubset reduced the size of all the presence of a metric; for example, you can ask the non-empty subset of descendants for specific units.

  NonEmptySubset is used to reduce the size of a set before analytical later retrieval. »

  The thing is once, I got this message and used NONEMPTYSUBSET and the warning does not go far so I found myself just ignore him. Some problems are simply complicated.

• Formula Member Essbase ASO (the order of resolution)

  Hello everyone,

  I was hoping to get some opinions on how they would handle a calc question I have.  I built a cube ASO (my first) for the loan on the housing data. A few fields I'm loading are a "Eff Int rate" and "Rate Eff Trans" (below) which are then used to calculate the 'interests Inc. or Exp' and 'transfer Inc. or Exp.

  Interest Inc or Exp =.

  CASE

  When IS ([account]. CurrentMember, [loan account]) THEN 0

  ON THE OTHER

  (([Avg Bal Mth] * ([taux d'Int Eff] / 100)) / [days per year]) * [days]

  END

  Transfer Inc. or Exp =.

  CASE

  When IS ([account]. CurrentMember, [loan account]) THEN 0

  ON THE OTHER

  (([Avg Bal Mth] * ([taux de Trans Eff] / 100)) / [days per year]) * [days]

  END

  

  The challenge I'll have and don't know how to manage in essbase is in what regards running sums.  I have a dimension labeled "Loan account" with about 15,000 members of individual accounts. For all the accounts of members, it works fine however when it gets to the cumulative of the 'loan account' it calculates incorrectly because of the aggregation.  To test, I tried isolating the different ways to make this work with my current solution (as seen in the above Calc) is to reset just the update rollup for now.  However, the ultimate goal would be to have this dimension of 'Loan account' always aggregate the information accurately.  Here's an example to help explain in more detail:

  

  For example, if I were to use the size of the attribute "Loan officer" and then drill at the low level of the 'loan account' it would recover 4 accounts and then those subtotal as stated above.

  I hope someone is able to give me some ideas or outline.  If this isn't the case, I can just try to accomplish in SQL before load my data.

  Thank you in advance,

  Bret

  Bret, I think what you see is a fundamental limitation of ASO.  Stored hierarchies are ALWAYS grouped together in front of a member formulas.  The only real workaround in Essbase is to use a procedural calc of the ASO - this would actually save results to the cube as input data that can then be wound the stored size.

• Can I do a free reference of a protected member MDX formula member account?

  My problem is:
  
  I need to make a free reference a member account.
  and the track is:
  -Cube Essbase ASO 11.1.1.3.
  -Accounts dimension has a member of level 0, called 'check '.
  
  The structure of the hierarchy is:
  Account
  -Level2 (+)
  -Level1 (+)
  -Balancesheet (+)
  
  I'm putting it under the formula of Member MDX on the 'check '.
  --------------
  CASE ([year]. CurrentMember)
  WHEN [FY10]
  Then
  Case ([period]. CurrentMember)
  When [JAN]
  Then
  < some logic here, pulling another Member here and works great >
  ON THE OTHER
  ([Balance sheet], [period].) CurrentMember.PrevMember) / * this is also working fine * /.
  END
  ON THE OTHER
  [Balance sheet] _ / * ERROR * / / * this IS WHERE it IS DEFAULT AND MAKING THE VALUES '0' for and year except FY10 * / _
  END
  -----------------
  
  
  Basically what I'm trying o realize is that I want ASO balance logic I write above ONLY for FY10 and don't do anything for any other year.
  When I don't write the last part "else", it makes the values zero for any year except for FY10. so I tried to put the logic above in the last part "else", but it is also not not and send me the "recursive [31] limit reached error»
  
  Any help on this appreciated.
  
  Thank you
  Ankit

  I'm still not clear on what you say, it seems that you say in a model of the ASO you can take a level 0 Member that has data in it, add a member formula he and Essbase will retain stored data that was there before the formula being added, but from now on he will use the result of the MDX formula.

  If that's what you say, it is not true. If you find that it is, then it seems to me be a bug. In my tests, it doesn't work that way, nor should it.

  Think about the consequences of not knowing if it's stored data or calc. by data. What do you do if you must reload the data? You cannot load the data of a member with a member formula, so you will have to remove the front form to load, then load and then add the formula back?

  There is something else here who is not be clearly explained.

  The solution is probably to create another stored for historical data and have then the Member with the formula reference this one for the periods you want and calculate for other periods.

• Formula of the sum in figures

  How do you create a sum of hour, minute column and multiple by a dollars an hour?

  For example,.

  10 h in the B1:B22 column

  $30 / h in C1

  Hi rp,.

  "The hours and minutes" are lasting and if multiplied by a number, will be a result that is also a duration. So the first step is to convert this length to a number that represents the hours (and part of an hour), then multiply this number by a second number that represents the rate of pay in the number of Dollars (and fraction of a Dollar) per hour.

  

  C2: = DUR2HOURS (B) * C$ 1

  D2: = DUR2HOURS (B) * D$ 1

  The values in the column of the hours are times.

  Values in C1 and D1 are numbers.

  Results in columns C and D are numbers, with the format of the cell value Currency with two decimal places.

  Table built in numbers (Numbers ' 09) v2.3. The formulas are the same in numbers v3.

  Kind regards

  Barry

• Formula Member

  
  Hi all

  I have the following formula: I created the below member of refrence other formulas that must be rolled: is there an easier way to re write these formulas with the Member?

  IF (@ISMBR ("FY15"))

  'Year '= 16;

  ELSEIF (@ISMBR ("FY16"))

  'Year' = 17;

  ELSEIF (@ISMBR ("FY17"))

  'Year' = 18;

  ELSEIF (@ISMBR ("FY18"))

  'Year' = 19;

  ELSEIF (@ISMBR ("FY19"))

  'Year' = 20;

  ELSEIF (@ISMBR ("FY20"))

  'Year' = 21;

  ELSEIF (@ISMBR ("FY21"))

  'Year' = 22;

  ELSEIF (@ISMBR ("FY22"))

  'Year' = 23;

  ENDIF

  Thank you

  Calvin replied before I could finish typing, but something like this:

  Year = @CalcMgrDoubleFromString (@SUBSTRING (@NAME (@CURRMBR (FYDIMENSION)), 2));

• Formula Member error: 'unknown member [&amp;] in [function name' - in SubVar SubVar

  I have a called subvar & DriverCrossdim that stores the location of crossdim of our financial drivers, so I need to paste the 8-Member crossdim whenever I have a reference driver. Is one of the members of this crossdim & BudgetYear. It works very well in Calc Scripts, but it is always fails when it is used in a formula of Member. According to me, because I put a subvar in my subvar. Is this a documented restriction of member formulas? Is there a way to get around that I can use?

  & DriverCrossdim value example:

  "NoEntity"-> & BudgetYear-> "NoCurrency".

  Personally, I wouldn't use a subvar for a static selection. But that's just my preference and not your question.

  I'm actually really surprised that you get away with this in in a calc script, so please teach me something.  I thought that the variables have been developed exactly once, so nested subvars would fail anywhere.  Obviously not, although I'm sure that's what happens in the form of Member.

  As a simple solution, maybe move & BudgetYear on the & DriverCrossdim variable, so that instead of...

  DriverMember-> & DriverCrossdim;

  .. .you tell...

  DriveMember-> & DriverCrossdim-> & BudgetYear;

  Still much shorter than eight dimensions.

• formula member to outline

  Hi all

  Can someone guide me on the member formulas in Essbase 11.x sketch. I read somewhere that we cannot have Member forms large contour that has an impact on performance. Can advise you on this and enlighten me to the best optimizations of contour...

  All that must be taken account in the use of the functions of essbase in member formula?

  Thank you for your sharing your ideas.

  Best practice is to use formula of Member on dynamic members in the dense dimensions.  Performance problems more frequently when you make dynamic Calc scattered members.  I don't think it matters how big the formula is.  What is important is the number of blocks needed to perform the calculation.

  Usually very good performance of the dense Dim formula

  Usually of slow performance of the sparse Sun formula

  Cross-Sun formula worse performance, cross dim in sparse dimension is the least desirable option.

• Calculation of the percentage formula Member

  I have a dimension of data type in an OSI application that is used to calculate adjustments to historical data. It is a dimension Label with only 3 members:

  Historical value

  Adj %

  Calculated Wo (dynamic member)

  Where I placed the following member formula in CalculatedAdj: CalculatedAdj = HistoricalValue * % Wo

  When validating the foregoing formula, I get the following error message "compilation error formula for [] (line 1): invalid assignment."

  I'm guessing that the formula is too simple and other parameters must be included, but I'm at a loss as to what they are. I appreciate your help.

  Hello f. Arabak

  If your synatax is exactly what you have written, then try this

  "CalculatedAdj" = "HistoricalValue" * "Wo % ';

  The special character needs quotation marks.

  He was missing the semicolon.

  Kind regards

  Philip Hulsebosch

• #Missing formula Member for upper level members should not aggregate?

  I have some senior level members in an application of ASO that shouldn't have grouped in them values. I seem to remember that there is a formula for Member #Missing I can put each of these members to prevent aggregated values. Does anyone know of such a formula of Member? Thank you

  Add a dummy Member under the parent

  Mother ~ (read only)

  Dummy member ~ (store)

  Ordinary child 1

  Ordinary child 2

  Ordinary child 3

  Just make sure that there is no data loaded against the fake member.

  Concerning

  Celvin

• Formula Member BSO using MDX ASO

  I use the Ref of the Essbase Tech to convert the below formula a calc to MDX member but just short. Help, please.

  IF ((@ISDESC (Cans)) AND (@ISMBR (Gander)))

  Total_Hours / @PARENTVAL (containers, cans-> Total_Hours); ENDIF;

  And my attempt to MDX:

  IIF ((IsAncestor [drums], [drums]. (CurrentMember]) AND (IS [Jars])),

  [Total_Hours] / ([containers], [cans].) CurrentMember.Parent, [Total_Hours]

  Thank you!

  When you use IIF statement you must specify the TRUE and the FALSE instructions.

  Change it as shown below and it should work

  IIF ((IsAncestor [drums], [drums]. (CurrentMember]) AND (IS [Jars])), ([Total_Hours] / ([containers], [cans].)) (CurrentMember.Parent, [Total_Hours]), missing)

  Concerning

  Amarnath

  http://Amarnath-Essbase-blog.blogspot.com

• Convert member formula Member MDX formula

  Hello

  I'm new to ASO and try to convert the following member formula in a BSO cube to an MDX formula for my ASO cube.  Any help will be greatly appreciated.

  IF (@ISMBR ("Q1"))

  ('TOTALREV' / ((@PRIOR («T4 «->» EOPDomains», 1, @RELATIVE ("exercice", 0)) + "EOPDomains") / 2)) * 4;

  ElseIf (@ISLEV("period",1))

  ("TOTALREV" / ((@SHIFT ("EOPDomains",-1, @ISIBLINGS ("Q1")) + "EOPDomains") / 2)) * 4;

  ElseIf (@ISMBR ("Jan"))

  ('TOTALGREV' / ((@PRIOR («Dec «->» EOPDomains», 1, @RELATIVE ("exercice", 0)) + "EOPDomains") / 2)) * 12.

  ElseIf (@ISLEV("period",0))

  ("TOTALREV" / ((@PRIOR ("EOPDomains") + "EOPDomains") / 2)) * 12.

  ENDIF

  It is a fairly easy calculation using a case statement. It is easiser a Calc script, since you can use Lag on all dimensions and tuples.  Try something like:

  Case When IS([Perioid].currentmember,[Q1]) then

  ([TiotalRev] / (([Q4], [EOPDomains], [Fiscal Year].currentmember.lag (1)) + ([period] .currentmember, [EOPDomains], [Fiscal Year] .currentmember) / 2)) * 4

  When IS ([Period].currentmember.levels (1)) then

  ([TOTALREV] / ((([EOPDomains], [Period].currentmember.lag (1)) + ([EOPDomains], [Period] .currentmember) / 2)) * 4)

  When IS([Period].currentmember,[Jan]) then

  ([TOTALGREV] / (([Dec], [EOPDomains], [Fiscal Year].currentmember.lag (1)) + (Period] .currentmember, [EOPDomains], [Fiscal Year] .currentmember) / 2)) * 12

  When Is ([Period].currentmember.levels (0)) then

  ([TOTALREV] / (([Period].currentmember.lag (1), [EOPDomains]) + ([period] .currentmember, [EOPDomains]) / 2)) * 12

  END

  Notes,

  1. you will need to check the skill parens and members for typos that I made this Freehand

  2 n-tuples as ([period] .currentmember, [EOPDomains]) might be able to simplify just ([EOPDomains]), but I made them full for consistenceny

  3. I suggest to change the order of the statements have the most frequent first, it can make the fastest formula

• Formula Member: IF... OTHERWISE describe the aggregation

  Hi experts,
  
  How to write a formula for a member parent entity as follows:
  IF (@ISMBR ("Member"))
  do something
  ON THE OTHER
  default hierarchical aggregation of his descendants
  ENDIF
  
  I want to just the 'do something' to run to some account in. If there is no ELSE statement, the formula will replace the hierarchical aggregation by default. The problem is that I can't find any manually default aggregate function.
  
  Please ask if my question is not clear.
  
  Thank you very much!

  Hello
  I got approach it slightly differently. I would not on the Member parent himself, instead I create another dynamic member in the same dimension and write the formula here.
  If (@ismbr (@list (list of accounts)))
  Parent1;
  On the other
  #missing;
  Endif

  Another alternative to write this in Parent1 would eventually end up with a formula too costly and complicated.

  See you soon,.
  Alp