Member of ASO formula - Concat

Similar Questions

• 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.

• Aggregation of a member of ASO with the formula of the IIR

  Hello

  I have a cube ASO has six dimensions. Based on the requirement, I need to have a calculated member (MBR1_CL) by taking the data from two members of entry (MBR2_IN & MBR1_IN) from specific intersections.

  I have written a formula of ASO member to the dimension of accounts MBR1_CL using IIR member below:

  IIF (IsAncestor ([West], [entity]. CurrentMember) AND IsAncestor ([ProdLine1], [Product]. CurrentMember) AND is ([years]. CurrentMember, & CYear) AND

  (Is ([period]. CurrentMember, [Jan]) OR ([period]. CurrentMember, [February]) OR ([period]. CurrentMember, [Mar])) AND

  IsAncestor ([CustCat1], [customer]. CurrentMember), [accounts]. [MBR2_IN]. Value, [accounts]. [MBR1_IN]. Value)

  The formula checks and working at level 0, but my request is related to the aggregation of month in the quarterfinals. MBR1_IN members & MBR2_IN gave responsible for all months, i.e. from Jan to Dec and when it is retrieved to Qtr levels it shows correct aggregated data, however for Member MBR1_CL which data takes the MBR2_IN for Jan, Feb, Mar months it does not show the correct aggregation in Qtr1 shows rather value of Member MBR1_IN in Qtr1. I set value of order of resolution as '2' for MBR1_CL, 3 'for Qtr1 and all other members being default ' 0'. Could you please help and suggest a solution to have correct data aggregated to all levels for Member MBR1_CL.

  Thank you

  AK

  Hi, AK,

  It's also what you say Essbase to do...

  (Is ([period]. CurrentMember, [Jan]) OR ([period]. CurrentMember, [February]) OR ([period]. CurrentMember, [Mar]))

  You don't say what it should do to T1. I just need the, [accounts]. [MBR1_IN]. Value

  Why should he aggregate the months?

  You will need to add all the logic of aggregation to the MDX. Yes, it will be a long script.

  It is perhaps easier to load the data into the appropriate location.

  Kind regards

  Philip Hulsebosch

• 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.

• Member of ASO Cube formula

  Hi all
  
  Work on Cube ASO (Version Hyperion 11.1.2). I am in need of suggestions with my formula of Member
  
  My Look of main lines as:--
  
  Account
  -Profit
  -Sales
  -GABLES
  
  CChannel
  -A001
  -A001-201
  -A002
  -A002-202
  
  Time
  -2010
  -QTR1
  -------------Jan
  -------------Feb
  -------------Mar
  
  
  
  Versions
  -Latest Version
  -V-003
  -V-002
  -V-001
  
  Now want to see my business is the current Version i.e.
  
  Let's say that
  
  Sales
  V-003 A001-201 100 Jan
  V - 002 Jan A001-201 #Missing
  A001-201 V-001 Jan 2000
  Current version A001-201 100 Jan
  
  V-003 here's my last and current V Version.If - 003 is missing, then v-001 will be my current version (IE Version = 2000)
  
  I wrote a current Version member member formula and the formula is
  
  
  * CoalesceEmpty([Current Version].) FirstChild.Lead (0), CoalesceEmpty ([Version]. FirstChild.Lead (1), [Version]. FirstChild.Lead (2))) *.
  
  Which works very well.
  
  Now, I came to know that the dimension Version 1000 members of level 0. The formula worked very well, but for 1000 members I must use the CoalesceEmpty function 1000
  
  That I don't want to do.
  
  Please
  Could someone help me with the code.
  
  
  Thank you in advance
  
  Kind regards
  RSG
  
  Published by: SG on January 26, 2011 11:12
  
  Published by: SG on January 26, 2011 11:15
  
  Published by: SG on January 26, 2011 11:15
  
  Published by: SG on January 26, 2011 11:25

  You can use 'NonEmptySubset' to the kids back just not empty, then use 'Head' to return the first of this set. In a quick test cube, it works:

  Sum (Head (NonEmptySubset (Children ([CurrentVersion])))

  Not quite clear why this "sum" is necessary, given that the 'head' without optional parameter must return only a member.

  This maintains the simple formula and requires no updates when schema changes, but the performance could be a problem because it will check all the children for the non-missing values fill the NonEmptySubset. May be a more elegant solution out there.

  Also to note that I am assuming that "NonEmptySubset (Children([CurrentVersion]))" always returns the subset in the pecking order - if this isn't, it won't work!

• On the conversion of the Member of BSO formula helps ASO

  Hello
  
  I'm new to MDX and got stuck on the conversion of function @IsMbr to ASO.
  
  Here's what my formula BSO
  
  JFK
  @ISMBR ("a") AND @ISUDA ("Account", "L"))
  « C » = « D » ;
  ENDIF
  
  Note: A, C, D and L are of different sizes.
  
  I am able to generate the formula of the BSO and I've tagged dynamic members top member. I have therefore been able to data aggregated.
  Formual to ASO works on lower-level members, but I can do together to ASO. She says all dynamics.
  
  Thanks for your suggestions.

  Hello

  There is a very good article in the MDX > Aggregate Storage topics > MDX contour forms Essbase technical reference which are necessary to carry out certain functions of BSO calculator examples of the MDX, the link to the 9.3.1 version is attached here.

  [http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_esb_techref/techref.htm]

  The @ISMBR example is slightly more complicated than what you need, what it is looking for a range of members, where you don't need one Member, so it should work (which assumes that you calculate 'Member C'):

  IIF (is ([Dim]. CurrentMember, [A member]) AND IsUda ([account]. (CurrentMember, 'L'), [member], missing)

  Please note that when the words are underlined in what above, they must appear in [but here assumes that it is a link and notes.] This formula is perhaps not optimal but it works for me.

  I'm afraid that my MDX skills probably don't extend far enough to help with your other point, it sounds as if you need a the IIF formula that performs a calculation if at level 0 and children are current Member if, at a level higher than 0, but I think that could involve a lot of orders "Crossjoin" and I have not tried those of front.

  Hope this helps
  Stuart Game

• BSO in ASO formula Conversion

  Hello
  
  Can you please help me in converting the BSO formula ASO. This is common is a member of the year (time) dimension.
  
  IF (@ISMBR (Current)) 'Member' = ('Member'-'member_In' + 'member_Out');
  ELSE 'Member' = @PRIOR (member);
  ENDIF
  
  Thanks in advance for your help.
  
  Kind regards
  UB
  
  Published by: user640496 on January 20, 2010 22:44

  Try something like

  CASE WHEN IS([Year].CurrentMember, [Current]) THEN
  [MCEB] - [Net_In] + [Net_Out]
  ELSE
  [MCEB].lag(1) END
  

  I just wrote this from memory, don't have the time to test at the moment, but should be close.

• BSO in ASO formula Conversion - need help

  ASO is not my forte... I'm trying to get a simple formula to work in cube ASO as part of the OSI - & gt; Conversion of the ASO.
  
  If this is the entity of level 0, the formula is (last shipped (PU) * Volume of the part)... works very well.
  If its higher level, it should simply add up the values of his children. The OSI equivalent that we use generally is @SUM (@CHILDREN (@CURRMBR("Entity"))).
  I tried the same thing in the ASO MDX script as shown below, it is not giving me good result... of ideas why this is not working?
  
  Thanks in advance.
  
  Nima
  
  Formula Member*.
  
  BOX WHEN ISLEVEL (Entity.CurrentMember, 0) THEN+.
  Last shipped (PU) Volume of the part x+.
  Else+.
  Sum (Children (Entity.CurrentMember))+.
  END+.
  
  Published by: Nima.V on November 12, 2008 19:12

  Have you tried to specify how you want the NAP?

  for example

  CASE WHEN ISLEVEL (Entity.CurrentMember, 0) THEN
  Last shipped (PU) x Volume of the part
  ON THE OTHER
  Sum (Children (Entity.CurrentMember), [measures]. [Part Volume])
  END

  also I'm not sure if the SUM is correct. This might work as it certainly specified tuples:

  SUM ({Products.CurrentMember.children}, [Measures]. [Part Volume])

  It will be useful,
  Gee

• BSO to ASO formula conversion

  Hi all

  I'm new with the ASO MDX formulas and I can't seem to understand the problem here for the help NOT in the formula.

  When I use IS in syntax of the formula withdraws, but when I replace it with NOT the slightest mistake what I'm doing wrong here? can someone help me reach this goal

  CASE WHEN (IS([scenario]. CurrentMember, [real])) THEN

  ([ACCT1] * [ACCT3]) + [ACCT2]

  END

  Basically, with the first line, I'm trying to achieve in OSB is IF (NOT (@ISMBR("Actual"))), but I can't convert that into MDX

  Any help will be greatly appreciated and links or documents that you can share for my to improve my skills MDX will also be appreciated

  Thank you

  I don't not a ton of experience with MDX, but my understanding is that IT is a function, it returns True or False, but is NOT an operator who basically returns a Boolean value, try using this:

  BOX WHEN (IS NOT ([scenario]. CurrentMember, [real])) THEN

  ([ACCT1] * [ACCT3]) + [ACCT2]

  END

  There is useful information about MDX in Essbase Technical Reference

• Member not pulling formula

  I have a situation where a member does not compute. Any help would be appreciated by explaining why it does not work.
  
  Outline
  A very simple pattern. The size of accounts had salaries, staffing and salaries. Salary is a member stored with a formula of staff * wages.
  
  Calculation
  DIFFICULTY)
  'Forecasts', 'FY12', 'work '.
  )
  "Wages."
  (
  IF ((@ISMBR ("FY12") AND @ISMBR("Apr":"Mar") AND @ISMBR ("Budget")) OR)
  (@ISMBR ("FY12") AND @ISMBR("Apr":"Jan") AND @ISMBR ("Forecast")))
  "Salary";
  ENDIF)
  ENDFIX
  
  Question
  It's getting fired a web form of planning, so I need the IF statement. As above, salary does not change. If a value exists, it remains. If it's #MI, there. If I change _ "Salary"; "Salary" = "Forces" _ * "wages"; _, it works as expected.
  
  I can't explain why the formula of Member isn't going to get fired? This isn't a question of creation of block.

  Normally, when you enter a member name in a formula, it triggers the formula of Member. However, when the name of the Member is inside of an IF statement, it ignores the Member form. When it is inside an IF statement, basically makes the Member equal to itself. So, you probably see nothing change.

  I hope this helps.

• Calc script for Member MDX formula

  Hello ASO brain trust
  
  I'm trying to move a member of ASO formulas calc script. Many parts of the calc script are piloted by the UDA.
  BSO
  
  ElseIf (@ISMBR (@UDA ("Entity", "NR_U41110")))
  "U41110"=@SUMRANGE ("R41100", @UDA ("Entity", "S_U41110"))
  + @SUMRANGE ("R41200", @UDA ("Entity", "S_U41110"))
  
  ASO
  IIF)
  IsUDA ([person]. CurrentMember, "[NR_U41110]"),
  Sum (CrossJoin ({"[R41100]"}, {UDA ([entity], "[S_U41110]" "")})) +.
  Sum (CrossJoin ({"[R41210]"}, {UDA ([entity], "[S_U41110]" "")}));
  0
  )
  
  
  It sounds good, but it won't scan.
  
  Any ideas how to get around the fact that the UDA does not work well with the cross join or the sum. Assuming that it is formatted correctly.
  
  Thank you

  IIF)
  IsUDA ([person]. CurrentMember, 'NR_U41110'),
  Sum (CrossJoin ({[R41100]}, {UDA ([entity], "S_U41110")})) +.
  Sum (CrossJoin ({[R41210]}, {UDA ([entity], "S_U41110")}))
  0
  )

  Try this. I removed the quotes of member names and I took the place of brackets from the values of the UDA which I guess do not belong there.

• How to convert the Member BSO formula formula ASO MDX

  Hello
  
  can someone help me to convert under the formula of OSB member to ASO
  
  T & M = "T & M"->"40000000 Services '%' Services:"-> "40000000;
  
  
  
  Kind regards
  Prabhakar.
  
  Published by: prabhakar on January 21, 2010 03:21

  Try something like

  ([T & M services], [40000000]) /([Services:],[40000000])

  You may need to tweak it to calculate a percentage of true

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Help formula ASO MDX

  Hello
  
  How can be function @ISMBR be translated MDX for a specific list of members? For example, how can we the BSO (@ISMBR("Jan","Mar","May","Jul","Aug","Oct","Dec")) converted to ASO formula?
  
  Any help is appreciated. Thank you!

  You will use the IS for a single member function and the function CONTAINS several members

  CONTAINS ([point]. CurrentMember, {[Jan] [Mar], [May] [Jul] [Aug] [Nov] [Dec]})

• Help with formula Mdx ASO

  Can anyone help me please with the conversion. I want to convert the below formula member of ASo Member mdx formula.
  
  IF (@ISMBR (@IRDESCENDANTS ("AID3EF")))
  '895672' - '237674 ';
  ON THE OTHER
  #Missing;
  ENDIF
  
  TIA
  
  Published by: user13146947 on December 14, 2011 09:19

  Yes, you are right, is to be GOLD.

  Kind regards
  RSG

  Published by: RSG on December 14, 2011 11:27

• 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.