Formulas in dimension in 10NW

When does the formula is executed for dimension?
At the time of report execution or seperately we have to excute it like script logic
Edited by: BPC Lover on Feb 10, 2012 6:30 PM

Formula in v10 haven't changed from v.7.x- it's executed at the time of the report. Formula has nothing to do with logic script.

Similar Messages

Creating a flag based formula for Dimension

Greetings everyone,
Hopefully this is simple answer. I have two dimensions "A" and "B" and a measure "C", where "B" is many to one attribute of "A", I would like to create a Flag formula in context that can characterise if a certain attribue of "B" is within "A".
For example:
"A"                "B"        "C"                          "MY FLAG"
ABC              123           12.31                        Y
BCD              123           10.54                        Y
BCD              104         107.83                        Y
BCD              105           11.32                        Y
DCE               101           11.30                       N
DCE               102           11.54                       N
DCE               125           12.00                       N
Pseudo Formula "MY FLAG" = If ("B" InList ("104";"123") In "A") "Y";"N") - however this formula creates "#multivalue" error.
Would like to use this flag as global indicator for other tables/ reports.
Regards,
Damian

What if you try using a max or min function in your formula?
= Max( If (<b> InList ("104";"123") In [A]) "Y";"N") )
Does it show the rigth results?

MDX dimension formula in BPC to get the previous month failed with parents

Hi,
I'm working on a proof of concept and I need to create a formula with the following requirement:
Requirement
Account2 = Account2 (Previous Month) + Account 1
Accounts -Jan-Feb-Mar-Q1
Account1_____15___25___45____85
Account2_____15___40___85___140     <== OK
Now, I was thinking of applying this formula within Dimension, using MDX. Then I tried with these two examples, but they didn't work when rolling up to parents. I mean, the calculation for every month works fine, but, the Total Quarter or the Total Year are wrong:
Attempt 1:
Account2.Formula = (ParallelPeriod([Time].[Month], 1, [Time].CurrentMember), Account2) + Account1
Accounts -Jan-Feb-Mar-Q1
Account1_____15___25___45____85
Account2_____15___40___85____85     <== WRONG
Attempt 2:
Account2.Formula = (Account2,[Time].PrevMember) + Account1
Accounts -Jan-Feb-Mar-Q1
Account1_____15___25___45____85
Account2_____15___40___85____85     <== WRONG
How can I solve this ? Should I use Script logic instead of MDX to perform this calculation ?
Thanks!
Diego.

DON'T use MDX script logic. It does not perform well under high data volumes or concurrency.
You're calculation can be done easy enough in SQL logic provided you scope the code correctly. Based on what you have given as requirements, the basic code would be something like:
*XDIM_ADDMEMBERSET TIME = PRIOR
*XDIM_ADDMEMBERSET ACCOUNT=A2
*WHEN ACCOUNT
*IS "A1"
    *REC(EXPRESSION=%VALUE%+GET(ACCOUNT="A2",TIME=PRIOR),ACCOUNT=A2)
*ENDWHEN
*COMMIT
The first two lines make sure you have the prior period values for A2 in the scope of exection. Then when a record for A1 comes through, it would take that value and add it to A2's prior value for the exact same intersection of all other dimensions. You would separately have to deal with moving forward values of A2 if there were cases where you could have a value for A2 in a prior period but not have a value in A1 for the current period.
Edited by: James Sharrett on Apr 14, 2008 9:51 AM

Problem Iif formula. MDX dimension formula

Hi experts,
I have a quite problem with tolerance in validation rules. When user tries to change Workstatus, system don't let it, because it detect that validation account is not equal to zero, however value of this account seems to be zero.
I know tolerance doesn't works fine on 7.0 MS version. Because of this we are trying to create an MDX formula on dimension account, but system give us this error.
- [CUENTA].[H2].[#X000] Parser: The end of the input was reached.
Our Dimension AccountL (Cuenta) has 3 hierachies. BLOQ_FASEC member is a parent member which sum all validation account.
We are trying to introduce a formula in other account member, giving to this one a tolerance.
Formula introduced is this one:
Iif(Cuenta.H2.BLOQ_FASEC < 0.5 and Cuenta.H2.BLOQ_FASEC > -0.5,0,Cuenta.H2.BLOQ_FASEC)
Could you help us?

Hi again,
Just to be on the same page...
- You have 3 hierachies in your Excel dimension file (PARENTH1, PARENTH2, PARENTH3)
- You have 3 Formulas columns in your Excel dimension (FORMULAH1, FORMULAH2, FORMULAH3)
- What I would like to know is, what are the dimension properties assigned to your dimension (Admin console --> Maintain dimension properties...). Here, you should ONLYhave one FORMULA dimension property assigned, even using multiple formula columns in you Excel file.
Then, if you setup that in that way, this is correct... But you should write your dimension formula only in FORMULAH2 column.
In fact, you cannot mix members from hierarchy 1 to calculate a member for hierarchy 2 for example. So, in one hierarchy you can just use members from that hierachy. Can you confirm that?
Then, could you also confirm that all your dimension formulas are using the correct syntax (WITH BRACKETS)..
Example: "[Cuenta].[H2].[BLOQ_FASEC]"...
Best Regards,
Patrick

Dimension Formula versus Script Logic that runs on default

Hi Experts,
Which is better to use dimension formula or script logic that runs on default? We have a lot of dimension formulas and when noticed that it has a huge impact in the performance of our AppSet. When we try to remove them, the performance seems better. We we're thinking of transforming these dimension formulas into script logic which will run by default instead. Right now I'm hesitant with two things, 1.) Will there be improvement in performance if I all these formulas are run at default via script logic? 2.) The maintenance seems to be much more complex for the user if we use script logic.
Thanks,
Marvin

Hi Marvin,
Actually you pointed very well the advantage and disantavage regarding dimension formula.
Dimension formula are executed into run time which means that value are not calculated. Of course this will have an impact regarding performances.
Usually our recommendation is to use dimension formula just when yoiu have KPI's to calculate which will be very difficult to be implemented into SQL scrip logic or when you have very simple calculation like Account A = Account B+ Account C.
For other calculation we advice our customer to use script logic.
But attention:
Default formula should not become very heavy because you will arrive into other issue with performances.
When you will send data if default formula script will be heavy you will arrive into situation to wait may be minutes just to send one figure and of course this will be not acceptable for users.
So you have to use script logic but you have to run into batch mode (schedule package) that script logic.
Into default formula you have to keep just minimum (you have to calculate just figures which have importance for user imediat, real time).
Also you have to be aware that moving dimension formula into scrip logic actually your fact table will grow a lot because the number of records generated will be probably 3-4 times bigger than number of records from fact table with dimension formula.
Maintenance of script logic is more complex than dimension formula and you pointed very well this.
So it is a balance and I tried o provide you suggestions or best practice when you have to use dimesnion formula and you have to avoid dimension formula.
I hope this will help you to arrive to best combination for your application.
Kind Regards
Sorin Radulescu

Dimension formula error

Hello all,
I have created the following dimension formula in dimension Groups(Currency):
'IIF([DataSrcDim].H1.CurrentMember is [DataSrcDim].H1.[20_ELIM], [GROUPS].MemberX-[GROUPS].MemberY-[GROUPS].MemberZ-[GROUPS].MemberW,NULL),SOLVE_ORDER=50
In short the objective of this formula is to perform a calculation (X-Y-Z-W) on GROUPS dimension members if the DATASRC dimension member is 20_ELIM.
However, I get the following error when I process the GROUPS dimension:
-"[GROUPS].[#ABCD] The dimension '[DATASRCDIM]' was not found in the cube when the string, [DATASRCDIM].[H1], was parsed"
I get this error even though the DATASRC dimension exists in th cube/application.
Would any of you have an idea why this error occurs and if so how can I correct it?
Thank you & regards
Raja

Hi,
Please try the formula as:
IIF([DATASRC].CurrentMember = "20_ELIM", [GROUPS].[MemberX]-[GROUPS].[MemberY]-[GROUPS].[MemberZ]-[GROUPS].[MemberW],NULL);SOLVE_ORDER=50
Hope this helps.

G/L Account Formula Variable

Dear All,
I want to take G/L Account value in formula variable, I have created using variable replacement path and key value populating in the variable. But it is not showing in the report. Can anybody give me suggestion on this.
Best Regards,
SGK

hi SGK,
Your wrong in doing formula creation . why bcoz 0gl_account is not key figure right. It is related to Dimensions. How u have created formula on dimension variable. If u want create formula variable it should have keyfigure Some times
with Time char ( ex: Keydate,posting date,clear date.... ).
Check it once.
Thanks,
kiran.

Help on writing a formula

Hi Guys,
I am trying to perform a currency calculation (not using the currency conversion). I am writing a member formula for
Dimension - Currency
Local - Store
Mark - Dynamic
Dollars - Dynamic [member formula example given below]
Dimension - Country
USA
Company 1 (UDA USD)
Company 2 (UDA DEU)
GER
Company 3 (UDA DEU)
Company 4 (UDA USD)
Everything is entered in Local currency.
This is what I am trying to do
Below member formula for 'Dollar'
If Level 0 member
If UDA (Mark)
USD = Local * 1.2;
If UDA (USD)
USD = Local ;
Else if
Aggregate parent
Endif;Endif;
This is what I am trying to achieve using the member formula for 'Dollar'. When it tries to calculate for Level 0 members - Company 1,2,3,4 it should perform calculation. If it's parent, then just add up. I hope I am clear. Here's a screenshot of what I am trying to achieve : http://img839.imageshack.us/img839/2764/currency.png
Regards,

Any idea?

Formulas Property Setup in Mulitple Hierachy

In SAP BPC v5.1 SP2 (soon to be SP3), we have formulas in dimensions that have Multiple hiearchies.
First, where is the official documentation for this setup? I found some unofficial alternative MS WORD documentation which tells us:
"If a dimension has multiple hierarchies you will still need to create an inapp property called formula, also ensure that there are inapp properties called formulahn for each hierarchy in the dimension"
We have been using ApShell - AccountL.xls as a guide:
In our dimension:
- We have added ParentH1 and ParentH2 and ParenthH3 to the dim.xls file
- We have added a user-defined property FORMULA using BPC Admin and marked it In app
- We have added three columns called FORMULAH1, FORMULAH2, FORMULAH3 in the dim.xls file.
But, do I need to add 3 inapp user-defined propeties of the same name (FORMULAH1, FORMULAH2, FORMULAH3)? In reviewing the back-end mbrDim tables, it appears SAP BPC generates these properties on their own.   The guidance above seems to be that I should also add in 3 User-defined properties called FORMULAH1, FORMULAH2, FORMULAH3 but I don't see any of that in ApShell Accountl.xls setup.
What is the preferred setup here? My main question is should I add three unique properties that the system seems to setup anyway and is there any plus/minue of doing that?
Mark

The process you desribed is correct. You do not need to add the additional FORMULAH"X" as an INAPP property or as a property at all. You do need, however, to verify that you set up statements in the SYSTEM LIBRARY, LOGIC LIBRARY, under MDXLIB.lgl, functions that look like th efollowing to save record lengths.
*Function Hir1(%Arg%)
     iif(AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%,Null)
*endfunction
*Function Hir2(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%, Null)
*endfunction
*Function Hir3(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2],%Arg%, Null)
*endfunction
They should be part of the ApShell already, but it is always a good thing to check. You may need to change the account dimension name to fit your model, and verify that the size of the FORMULA property has ample space, such as 250 or 450 characters.

BPC75NW - Workbook Options & Refresh Options Issue

We are on SP9 with Client 9. The issue is that in the Workbook Options, Refresh Options section the boxes to indicate refresh preferences are not accessible..instead they are "greyed" out. The box to Allow Changes by Users is OK..white box and checked. Impact on the reports is that cells containing EVCVW formulas for dimension member changes are not refreshed by a double click on the cell to select a new member...instead the old member stays put in the cell. However, the Action Pane CVW is updated with the new member selection. Executing the report results in the right data and updated cells in the body of the report. However, this is not correct behavior or so it seems. Why are the Refresh Option boxes inacessible - "greyed" out? How do we fix this so that the boxes are white and accessible to users once again?
Thank you.

This issue was resolved by uninstalling and reinstalling the client 9 BPC application. I'm still not sure why it occurred in the first place, but it is resolved.

Can I split the contents of characteristic into two key figures?

Hi experts
I have a characteristic that represents a discount. It is entered into SAP as Nnn or Pnn where N means negative and P means positive and the nn is a two-digit number.
Within my query, I need to be able to add this discount to another discount type (which IS conveniently entered as -nn.nnn!) and get "total discount". If I can get the N/P and nn parts of the characteristic into separate key figures I'll be able to create my "total discount" formula.
This would be so simple to do in code, but can I do it within the query?
Thanks for any guidance
Brigitte

Ravi
I already tried that but couldn't get it to work. I thought the offset stuff would do the trick but it didn't work - I just got 0 instead of the two-digit number I was expecting. (I put in offset start = 1, offset length = 2 to try to get the nn part of the characteristic.) Also, I couldn't figure out how to get the N or P part of the characteristic as the formula variable dimension doesn't allow characters.
If you can be more specific about what I should be doing, please reply and I will try what you advise.
Thanks
Brigitte

Budget to Actual Variance Formula in Scenario Dimension help

I am trying to calculate the Budget to Actual variance by using a member formula in the Scenario dimension.
The formula I'm using is: @VAR("Final"->"Actual" -> &CurrentYear,"Budget");
This formula yields a value that equals the budgeted amount.
The Variance % formula I'm using is: @VARPER("Final"->"Actual" -> &CurrentYear,"Budget")/100;
This % formula equals 100% for most accounts, but is 200% or 300% for other accounts
What am I missing? Many thanks in advance

Jake,
I'm a newbie, so I'm not sure what you mean by cross-dim. I didn't write the formula but it's up to me to figure this out. Yes, I do want to compare budget data to same year actual data.
It is dynamic. A sample retrieve for -200% would be Total Operating Revenues:
Actual = 2,404,789
Budget = 2,117,250
Variance $ = (2,117,250)
Variance % = -200%
A really crazy one is Benefits Rollup:
Actual = 66,353
Budget = 73,817
Variance $ = 73,817
Variance % = 500%
I appreciate your help very much.
Max

BPC 7.5NW SP08: "unknown MDX error" message for simple dimension formula

Hi everyone!!
We are facing many different issues concerning dimension formulas and
script logic. Maybe it's something related to SP08. For instance,
consider the following:
- there is a dimension named P_Account, with members Price, SalesCost,
and others
- there is a dimension named P_Product, which consists of a hierarchy,
for instance: Prod1 with two children, Prod1A and Prod1B
We want to set the following dimension formula in P_Product for Prod1 member:
IIF([P_Account].CURRENTMEMBER.PROPERTIES("ID") = "Price", Null, 1)
that is, we wanted to try to be able to avoid summing Price, returning
Null for (Price, Prod1). Later we would try to replace "1" with the
appropriate formula to sum children of Prod1 for all other members of
P_Account. The result is an odd error: "MDX statement error: unknown MDX
error" (or something similar, since I get the error message in portuguese).
We have spent almost two days studying alternatives in SDN Forum, blogs,
google, etc, trying to find a reason for the error but couldn't find it.
Could anyone help on this one?
Thanks!
Luigi

Hi everyone!
After contacting SAP, we were asked to try to reproduce the error in APSHELL. I did the following:
1) created another application set, copying APSHELL, named it TESTAPPSET;
2) added two members to dimension P_ACCT (ID, ACCTYPE, SCALING, RATETYPE):
   (PRICE, INC, Y, END)
   (SALESCOST, INC, Y, END)
3) saved to server and processed P_ACCT dimension successfuly
4) added a UD dimension copied from P_Activity, named P_Product
5) deleted all members of P_Product, processed the dimension sucessfuly
6) added FORMULA property to P_Product, with size 200
7) added three members to P_Product (ID, PARENTH1)
   (Prod1, "")
   (Prod1A, Prod1)
   (Prod1B, Prod1)
8) saved to server and processed the dimension successfuly
9) edited P_Product members and added the following as FORMULA for Prod1:
IIF([P_ACCT].CURRENTMEMBER.PROPERTIES("ID") = "PRICE", Null, 1)
Result was sucess!!
10) edit P_Product again and removed the formula, saved to server and processed dimension successfuly;
11) created an Application named SALES, type Financial Report, copied from PLANNING with dimensions
12) edit dimensions, removed P_Activity and added P_Product to the list
13) went back to step (9) and tried to add the formula again, saved to server and processed P_Product dimension. Result was success again!!
So I imagined the issue might be caused by the user I was log in with. I went back to our application set, logged in as BPC_SYSADMIN and tried to set the formula again and it didn't work. User was not the problem.
Since I had tried all the above creating everything with all UPPERCASE, I decided to try the following Formula
IIF([P_ACCOUNT].CURRENTMEMBER.PROPERTIES("ID") = "Price", Null, 1)
that is, P_ACCOUNT instead of P_Account. Result: success in processing dimension!!! And the formula worked as expected when I opened an Input Schedule to test it.
When I check my dimension list in BPC Admin it says P_Account (mixed case), instead of P_ACCOUNT (all uppercase) since it was the way we created it.
So, I spent 1hour to do the whole test, but it worked. I sent two questions/requests for correction or improvement to SAP:
I) which case should be used in formulas? given I see P_Account in Dimension list, how should I know that I should write formulas with P_ACCOUNT, all uppercase?
II) could BPC provide more descriptive error messages when processing dimensions and validating script logic? a simple error message such as "unidentified command or reference at P_Account" or anything similar would have saved us 4,5 days of work! it's a lot!
Thank you guys for your support!!

Help! Hyperion Planning Dimension formula no longer works after name change

Hi,
I am having an issue with Hyperion Planning. I recently changed an account's dimension name from ASales & Property Taxes (D) to AProperty Taxes (D). However, the original name was used in a formula of another account. When I ran my refresh I got the following error:
Error [1200354] detected in member formula for member "AFacilities Costs as a % of Revenue".
So I went into planning and went to the referenced account and looked at the formula. The formula still had the old member name ASales & Property Taxes (D) so I changed the formula to the new name AProperty Taxes (D). However, when I went to validate the formula I got the following error message:
Error compiling formula for [] (line 1): expected type [NUMBER] found [STRING] (["ASales & Property Taxes (D)"]) in function []
However, my formula has the new name not the old name. Here is my formula:
("AMaintenance (D)" + "AMaintenance (SG&A)" + "ANon Cap Equipment & Rentals (D)" + "ANon Cap Equipment & Rentals (SG&A)" + "AOperating Leases (D)" + "AOperating Leases (SG&A)" + "ARent & Occupancy Costs (D)" + "ARent & Occupancy Costs (SG&A)" + "AProperty Taxes (D)" + "AProperty Taxes (SG&A)" + "ASecurity (D)" + "ASecurity (SG&A)" + "AInsurance (D)" + "AInsurance (SG&A)")/ARevenue;
Does anyone know how to fix this problem? Please help, as a result of this issue none of my accounts or clients are getting pulled into the Balance Sheet causing it to not tie with Oracle :( Thanks!!

Hi,
What happens if you try and refresh with updating the formula to reference the correct name?
You won't be able to validate the formula because the member does not yet exist in essbase until the refresh has completed.
If you have problems you could always, remove the formula and store it, refresh so the new member gets created, then put the formula back and refresh again.
Cheers
John
http://john-goodwin.blogspot.com/

Error during scoping of dimension formula

Hi
I am working on the microsoft 7.0 version - SP04.
I havewritten a MDXformula on an Accounts dimension member as follows:
IIF([DATASRC].[INPUT],
IIF([TIME].CurrentMember.children.count=0,
(Account].[214],[DATASRC].[TOTALADJ],[ACCTDETAIL].[F_NONE])-(Account].[214],[DATASRC].[TOTALADJ],[ACCTDETAIL].[F_OPE])),NULL),
SUM(DESCENDANTS([TIME].CURRENTMEMBER,[TIME].[MONTH],LEAVES)))
ACCOUNTL=My account dimension name
214=parent account
I expect this to give me the following result (logic behnd the formula)
If the current member is a leaf level time period, difference detween the value at total adj levelin datasource at F_NONE (all my inputs are at F_NONE) and value of opening balance atF_OPE (whic h i will use the the account transformation rule to get).
But on trying to validate the formula or process the dimension, i get a pop up showing all account memebersas deleted and then another error message that there are nombrs in fact table to process .
I do not get this msg if I remove the first IF condition of [datasrc].[input].
Basically,I want to scope the formula to work on one datasource member ,and allow dataentryat other dataSOURCE members for the same account.
I think SQL statements may also help --but the syntax of this does defeat me at this time.
Request inputs on what may be causing this.
Pankti Shroff

Hi,
I have a feeling that the problem is with the application and not with the dimension. But to check that, we need to do the following.
1. Do the processing and check only "validate formula". See what are the errors.
2. Process the dimension without selecting any application.
Let me know the results.

Formulas in dimension in 10NW

Similar Messages

Maybe you are looking for