BPC Netweaver dimension formula SUM and AGGREGATE

Hello
Does anybody knows the arguments we can use with SUM and AGGREGATE in a dimension formula in BPC NW.
I would like to aggregate data on a hirarchy but not from leaf level only the child at a specific level (do an average at a certain level and then do an aggragate of the children at upper level).
Any idea how to use CHILDREN with SUM or AGGREGATE ?
Thanks
Regards

Hi Anne,
Note [1550366|https://service.sap.com/sap/support/notes/1550366] solves part of your problem (in SP06), but these formula results will not roll up the hierarchy and you still cannot reference formula members within formulas, so you will not easily be able to aggregate the averages that you calculate.
It would probably be better to calculate your averages in script logic and assign them to normal base members.
Ethan

Similar Messages

MDX Dimension formula - sum using property

Hi All,
I am trying to add a dimension formula on the account dimension sheet and the goal is to add all the accounts that have a property TEST='Y' into a new account TESTACCOUNT
Here is the formula that I am using but it errors out while processing.
ID----
FORMULA
TESTACCOUNT----
SUM([ACCOUNT].[H1].properties("TEST")="Y"),solve_order=10
Can you please tell me where I am going wrong.
Thanks in advance for your help.
Swaroop
Edited by: SwaroopLalam on Aug 13, 2009 4:18 PM
Edited by: SwaroopLalam on Aug 13, 2009 4:19 PM

Hi Petar,
Thanks for your prompt reply. I tried the following and even that did not work. Am I doing something wrong here? Please see the error I received while processing the dimension;
'sum(FILTER(descendants(ACCOUNT.[TESTACCOUNT],99,leaves),account.properties("TEST")="Y"),measures.periodic),solve_order=15
ERROR:
- [ACCOUNT].[H1].[#TESTACCOUNT] CustomRollupFormula([Account].[Account_H1_ID6].[TESTACCOUNT]) (1, 61) The 'Account' dimension contains more than one hierarchy, therefore the hierarchy must be explicitly specified.
after that I gave the Heirarchy [H1], below;
'sum(FILTER(descendants([ACCOUNT].[H1].[TESTACCOUNT],99,leaves),account.properties("TEST")="Y"),measures.periodic),solve_order=15
ERROR:
- [ACCOUNT].[H1].[#TESTACCOUNT] CustomRollupFormula([Account].[Account_H1_ID6].[TESTACCOUNT]) (1, 65) The 'Account' dimension contains more than one hierarchy, therefore the hierarchy must be explicitly specified.
Thanks,
Swaroop
Edited by: SwaroopLalam on Aug 17, 2009 5:14 PM

How to get two Results - Sum and Average for one KeyFigure

I have "Material" in Rows and "Cal Year/Month" in Columns and also KeyFigure "Qty" in Columns.
The Results (Yellow) of "Qty" is defined as "Avg of all values <>0". This works fine but how do I get two Results - one is a "Sum" and the other "Avg" for just one KeyFigure. The output basically should look like below:
      Cal Yr/Month 01/2006   02/2006   03/2006...    Result        Result
Material                   Qty       Qty           Qty       Sum of Qty   Avg of Qty
ABC                       100         0             200            300             150
DEF                       100         200          300            600             200
GHI                        500         300          400           1200            400

Hi Srinivas,
I think you must use Restricted Key Figures and Formula.
Do not introduce CALMONTH in columns, but restrict 12 times the Key Figure Qty with 0CALMONTH3, that is 01-02-03-...
Then create a Formula that is the Sum of all Restricted KF and call it SUM.
Then copy the previous Formula (SUM) and call it AVG and give the option of Average of all Values <>0.
Try.
Ciao.
Riccardo.

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!!

Using Dimension Formulas to sum data based on different criteria

Hi all,
I am trying to use a u201CDimension Formulau201D to perform the following calculation:
We have an account dimension which has 2 important properties:
1.     CRITERIUMTYPE: This property can have 3 different values: u201CWERKu201D, u201CINVu201D OR u201CLIQu201D
2.     ACCTYPE: This property can have 2 different values: u201CEXPu201D or u201CINCu201D
The client wants to have a report that sums data based on these 2 properties. An example will help to clarify this:
ACCOUNTS     CRITERIUMTYPE     ACCTYPE     VALUE
ACCOUNT A         WERK                          EXP               100 u20AC
ACCOUNT B         WERK                          INC               150 u20AC
ACCOUNT C         WERK                          EXP               200 u20AC
ACCOUNT D         WERK                          INC               300 u20AC
ACCOUNT E         INV                          EXP               50 u20AC
ACCOUNT F         INV                          INC               100 u20AC
ACCOUNT G         INV                          EXP               200 u20AC
ACCOUNT H         INV                          INC               500 u20AC
The clients wishes to see this data in the following way:
CRITERIUMTYPE     ACCTYPE     VALUE
   WERK                         EXP              300 u20AC
                                    INC              450 u20AC
   INV                         EXP              250 u20AC
                                 INC              600 u20AC
In order to achieve this I have created several new accounts, one for each combination e.g.: Account WERKEXP is used to sum the data on the combination CRITERIUMTYPE=WERK and ACCTYPE=EXP. I have created a dimension formula in my account dimension but this is where I am stuck. I have created the following formula to calculate the account WERKEXP:
IIF([BUDGETPOSITIE].CURRENTMEMBER.PROPERTIES("ACCTYPE")="EXP",IIF([BUDGETPOSITIE].CURRENTMEMBER.PROPERTIES("CRITERIUMTYPE")="WERK",[BUDGETPOSITIE].CURRENTMEMBER,0),0)
The problem with this formula is the following:
The formula will add all amounts that meet the 2 criteria mentioned in the formula, EXP and WERK, but as soon as it finds an accounts that does not match the 2 criteria it will set the account WERKEXP back to 0. I need to know if there is a way, using dimension formulas, of adding these values together without the new account being set to 0 as soon as one of the accounts it needs to check does not meet 1 of the 2 criteria.
We are working on SAP BPC 7.5 for NW with SP04
All help is very much appreciated!
Kind regards,
Stefano

Hi,
You can also use ParentHn property to have different grouping of accounts within the dimension.
So in your case rather using the member formula you can have four accounts and add them in the Parenthn property for grouping it.
1. The Solution proposed by Nilanjan is specific for a Report/IS and Performance will be good
2. My solution will be global something similar to MDX formula, but performance may be slightly lesser than using excel function.
Hope this helps,
Regards,
G.Vijaya Kumar

BPC Netweaver version - Conversion File Formulas

BPC (Netweaver) Expert,
When creating formulas on the Data Conversion File that is called by the Transformation File, the Formulas are not working on the Netweaver Version. Does anyone have any idea what may not be set up correctly?
Thanks,
Greg Rotvold

Hello Greg,
BPC Netweaver uses somewhat different syntax for conversion formulas, and uses javascript for complex formulas, so formulas written using Visual Basic on the MS version will not work, though the basic *IF logic should work (I think I'm remembering MS conversion formulas correctly, but it's been a while). You can find the relevant Netweaver version documentation here: [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/81/94a8a5febd40268d5c59b4fc31be37/frameset.htm]
If you want help specifically on the Netweaver version I suggest you ask your question in the Netweaver forum. I'm not sure what forum is most appropriate for questions about the differences between the two versions
Ethan

SAP BPC - Recursive Dimension Member Formulas

Hi BPC community,
We have a customer requirement to create recursive dimension member formulas. Has anyone dealt with this topic before?
Example:
Account A = Account B * .05
Account B = Account A + Account C.
Account D = Account B * .10
Thanks,
Jeff Holdeman
EPM RIG

Hi Nicolas,
Thanks for pointing us in the right direction. The math actually turns out a little different, as I think you slipped a decimal. But none the less, your contribution is MUCH appreciated.
Here is the proposed solution. For more details, we also need to utilize the solve_order parameter to force the system to calculate the dimension formulas in the proper sequence. Zero is the highest priority.
Assume...
A = B * .05
B = A + C
C = input
D = B * .10
Therefore solving for B...
B = (B * .05) + C
B = .05B + C
B - .05B = C
.95B = C
B = (1 / .95) * C
And...
D = (1 / .95) * C * .10
For example, if C = 100...
B = (1 / .95) * 100 = 105.26
A = 105.26 * .05 = 5.26
D = 105.26 * .10 = 10.53
I'll assume there are two accounts for "C"; one for input and one as a formula.
[Account].[C] = [Account].[C input][, solve_order = 1]
[Account].<b> = [Account].[C] * 1 / .95[, solve_order = 2]
[Account].[A] = [Account].<b> * .05[, solve_order = 3]
[Account].[D] = [Account].<b> * .10[, solve_order = 4]
Edited by: Jeffrey Holdeman on Aug 11, 2008 5:58 PM

Dimension,Dimension Member,Property and Cube in BPC

I am learning BPC. I've knowledge on relational database.
Please help me in understanding Dimension,Dimension Member,Property and Cube.

Hi,
Please refer to the below link from help.sap:
http://help.sap.com/saphelp_bpc75/helpdata/en/5A/69200C88AA40C9B18844A25259F147/frameset.htm
This link will guide you through all the BPC concepts.
Hope this helps.

Dimension formulas+aggregate

Hi gyus!
Have i got it right, that members that was calculated using dimension formulas can't be aggregated in time dimension.
for example
Member P_ACC1 is calculated as PACC2*PACC3
so
________ Q1    jan    feb   mar
P_ACC1    81      9     9    9
P_ACC2    9        3     3    3
P_ACC3    9        3     3    3
but i need smthng like this
_________ Q1   jan    feb   mar
P_ACC1    27      9     9    9
P_ACC2    9        3     3    3
P_ACC3    9        3     3    3
is it possible to archieve it using dimension logic?
Edited by: susersuser on Jan 25, 2011 9:31 AM

Try using SOLVE_ORDER=0 in dimension formula for P_ACC1.
Check the link http://help.sap.com/saphelp_bpc75_nw/helpdata/en/79/3643be0cec44cc819cf3c7e697b2b7/frameset.htm for more information on SOLVE_ORDER.

Dimension formulas & SQL AS 2005

I'm in the planning process right now for the upgrade from 4.2 to 5.1. We have already had a technical with SAP and recently one with the consultants that will be assisting us with the upgrade. One of the main concerns that our consultants had was the amount of dimension formulas that we have within our application. They spoke about an issue with MS AS 2005 and the performance hit associated with dimension formulas. They also said that Microsoft would not be addressing this within SQL 2005, but that there would be a fix in 2008. That being said, I have 2 questions.
1) Does anyone know if there is a MS Knowledge base article that I can reference?
2) Does anyone have any advice for where to begin addressing the dimension formulas and moving them into business rules and/or sql?

It has always been the case that you should avoid using MDX for formulas that cannot be calculated at all levels with the same rules. Though Ive seen lots of cases where people write a lot of MDX that should never have been written and could be done better in either scripting logic or spreadsheet logic. Lots of nested IIF statements or other complex expressions will generally perform poorly. If AS cannot use aggregations or the formulas are sufficiently complex that AS cannot determine for sure if it can use the aggregations then it will perform the necessary aggregations at query time to derive the values. This ABSOLUTLY kills AS performance. The major performance factor in AS is the pre-aggregations as far as query time goes.
For example you can do a Units x Price calculation in MDX and write the formula so that it will be correct at the base members and all rollups. However, if you pick a top level member the query will run forever because AS will calculate every leaf level UxP calculation below the level you are at across the hierarchies and then aggregate all the values to derive the correct value. Ive seen calculations like this run for hours. This is the entire reason that scripting logic was created to allow these types of calculations to be executed in the relational store and the results aggregated along with the other data in AS.
MDX should only be used for things such as basic reporting ratios such as Gross Margin Pct which is simply [Gross Margin]/[Sales] regardless of the level you are at in the hierarchies and will easily use any aggregations that are available at the intersection that the query is requested for. This is true for AS 2000, 2005 and Im sure it will be in 2008. This has nothing to do with BPC, its simply the strengths and weaknesses of AS.
What we have seen is that in AS 2005 it is more prone to performance issues so greater care in how a formula is written is needed. Also, with BPC 5.x the way multiple hierarchies was changed as discussed earlier so even Gross Margin Pct become a more complicated formula in the presence of multiple hierarchies (in the dimension that the formula is written in) just from the syntax required to qualify out the various hierarchy cases.

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

Error in Dimension formula to find the average price

Hi all,
I have tried a dimension formula to find the average price of Product.
if the product is a parent level member then average price should be the average of the list price,other wise it should be the list price itself.
IIF([PRODUCT].CURRENTMEMBER.PROPERTIES("CALC")="N",[KEYFIGURES].[LISTPRICE],AVG(DESCENDANTS([PRODUCT].CURRENTMEMBER,[KEYFIGURES].[LISTPRICE],LEAVES)))
While i tried the same i received some strange error , i don know whether its having some dependency on the Customer dimension. since K0030101 is a memebr belonging to CUSTOMER dimension.
MDX statement error:"Value K0030101 for characteristic /CPMB/U6D7SXT un"
I'm not sure whether its an error with the formula i created or any dependancy issue or whether this scenario is possible using dimension formulas or not.
Thanks in advance .
Anila Mohan

Hi everyone!
We are using BPC 7.5 NW SP08 and we've had the same error message while adding a formula to the Account dimension:
'MDX statement error: "Value 1 for characteristic /CPMB/S9D7Q23 un".
We then checked in BW for /CPMB/S9D7Q23 and found out that it was the Product dimension.
The solution for the issue was quite interesting. I had seen in another post that sometimes CALC property was not correctly determined for SP08. The solution proposed was to edit dimension members, clear ParentH1 column, process dimension, re-edit, paste back ParentH1 values and process dimension again. This corrected CALC property problem.
It also worked for my case. After doing it to Product dimension I tried again to set the formula in Account dimension and it worked!!
Hope this helps.
Regards,
Luigi Laporte

Automatic hierarchie aggregation not working when dimension formula is used

Hey folks,
i'm facing the following issue. currently i'm setting up an application to plan sales quantities, prices and manufacturing costs.
subsequently i want to calculate following values for members of account dimension:
- turnover (price * sales)
      -> implemented as dimension formula
      -> in the account hierarchie it's a child of net revenue
      -> account type: inc
      => calculation work fine in the reports
- manufacturing cost (manufacturing cost * sales)
      -> implemented as dimension formula
      -> in the account hierarchie it's a child of net revenue
      -> account type: exp
      => calculation work fine in the reports
- net revenue (turnover - manufacturing cost)
      -> in the account hierarchie it's the parent of turnover, manufacturing cost
      -> account type: inc
      => key figure is empty !!
As far as i understood BPC is aggregating automatically along the hierarchie. That means to me that net revenue should be automatically calculated due to the hierarchical relation in account dimension.
Did anyone ever face same issue ? probably the hierachical aggregation is not working when key figures based on dimension formula is used !? Do i really have to implement script logic to solve this issue ?
Looking forward to interesting approaches to solve this issue !
Best regards,
Moritz

Hey,
sorry my description was misleading at this point. i don't have a formula define for net revenue dimension member. i expected the system to automatically calculate it by aggregation along the account dimension hierarchy where net revenue is parent to the turnover and manufacturing costs which are calculated by dimension formula.
Best regards,
Moritz

How to remove locks in BPc netweaver?

Hi all,
How to avoid locks and how to remove locks in BPC netweaver and what is meant by concrete locks and work station locks in bpc netweaver ?
Thanks
Pooja

Hi Pooja,
There is a good deal of documentation on Work Status and Concurrency Locks in the Application Help.
I would start there.
http://help.sap.com
Cheers, Scott

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/

BPC Netweaver dimension formula SUM and AGGREGATE

Similar Messages

Maybe you are looking for