Dimension formula values

I have dimension members values with formula. Though values are generated at member level,at the parent hierarchy level the values are not getting rolled up.
I am in BPC7NW...any suggestion , inputs welcome...

D,
I think there is some miss communication between your question and my answer..either i'm not able to understand it correctly
pls answer these questions.
1)your formulas are getting calculated and right amnts are posted to the base level?
2)how are you checking it.?
3)refresh your client DIM files under options in your EVDRE and check them again..
again...if the correct values are posted to your base members...the mdx formulas job is done...
for rolling it up to the parents is your BPC job (cube, hierarchy,report)
why dont you try writing the same formula on the APPSHELL Copy and check the results...
hope this helps D....
I cant think of anything else...

Similar Messages

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

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

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

Transaparent partition formula value not reflect in trgt cube

Hi All
I created transaparent partition data is reflecting in the trgt cube but we are calculating member formula for srce cube that values are not reflectin in the trgrt cube I excute design aggregation for srce db still its not reflecting the value s of calculated member, Any help would be appriciated.;
thanks

Tanku
we are using formula in that formula we are using thre dimension crossing
1 flow
2 indicator
3 period
I am patitioning @idescndents(2009) its not showing
second i tried this @idescndents(2009) @ idescendents(indicator)
third i tried this also @idescndents(2009) @ idescendents(indicator)@idescendents(flow)
we have the formula for flow dimension
srce and trgt have the all are same dimns , evrything is same , but its not reflecting int to trgt
plz help on this formula value is it reflect in trgt????
Thanks

Dimension Formulas in NW

Hello All,
I am trying to implement account dimension formulas for the calculation of ratios, but while it is processing successfully, I am not seeing any results.
A couple of questions:
1. Do dimension hierarchies have to be qualified in NW as it does is MS?
2. Does the function Val not work in NW? I am trying to use the value in the weeksinperiod property of the time dimension in the formula. In the MS version, I used to have to convert the property value to a numeric value in the formula. When I use it in NW, I am getting as error for the function, Val.
Below is my formula. If anyone could offer some guidance, I would really appreciate it.
IIF([AccountCC].[EARNED_HOURS_2]=0,NULL,[AccountCC].[EARNED_HOURS_2]/[TIME].CURRENTMEMBER.PROPERTIES("WEEKSINPERIOD"));SOLVE_ORDER=4
Regard,
karen

I just noticed the message removed the brackets around my dimension names. I forgot to set the formula as code. Here it is again.
'IIF([AccountCC].[EARNED_HOURS_2]=0,Null,[AccountCC].[EARNED_HOURS_2]/[TIME].CURRENTMEMBER.PROPERTIES("WEEKSINPERIOD"));SOLVE_ORDER=4
Regards,
karen

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

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.

How can we remove the commas from the Formula value in SAP BW BEx query

Hi All,
How can we remove the commas from the Formula value in SAP BW BEx query
We are using the formula replacing with characteristic.The characteristic value needs to be display as number with out commas.
Regards
Venkat.

Do you want to remove the commas when you run the query on Bex Web or in RSRT?
Regards

Is it possible to pass a formula value from a sub-report to a main report

Hi there,
Im trying to pass a formula value from a Sub-report back upto into my Main report but the value doesnt seem to be getting passed up. Ive tried it the other way around, that is, passing a value from the main report to the sub-report and that works fine.
Below is an example of what I am trying to do but it is not working. In my sub-report Ive declared a formula variable as,
formula name=main_subIntRatePageCount
Shared NumberVar subIntRatePageCount := TotalPageCount;
and in the Main report Ive declared the formula variable as,
formula name=subIntRatePageCount
Shared NumberVar subIntRatePageCount;
subIntRatePageCount;
I want the value assigned to "subIntRatePageCount" in my Sub-Report to be available to my Main report.
The problem I am trying to solve is that the sub-report is spilling over onto two pages, and I need a way of updating the page display on the main report to reflect this. The page display is of format, "displaying page 1 of 3", but its not taking into account the extra page produced by the sub-report, so it should say "displaying page 1 of 4".

Also thanks Raghavendra, Asha,
I've tried adding the "whileprintingrecords" statement but that doesnt seem to make any difference.
I notice that the subReport is being called from my the GroupFooter section of the main report, and I am trying to reference the variable in the main repot in the Page Footer section. Could it be that the variable hasnt been calculated in the Page Footer by the time I calculate it in sub-Report? I thought Crystal Reports does at least 5 passes over the report evaluating all the formulas before it prints the report?
The problem Im trying to solve is I need to know how many pages my report will have before its completed, so that i can print the statement "displaying page 1 of X", and X is currently not being calculated correctly because the sub-report is printing onto 2 pages and not 1 so the report thinks I have 1 of X pages and not X+1.
Regards
Robert.

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

Only Dimension Table Values in Combo Box or Drill Down Selections

Hi All,
How to get only Dimension Table Values instead of Master Data Values in Combo Box or Drill Down Box list of values?
I am getting all the values in 0CALMONTH Combo Box where i need only infoproviders values.
In Entry List tab of Combo Box when i select 0CALMONTH its reading from its Master Data.Is there any option how there is Dimension table in Value help.
In Query, infoobject levels the filter values selection is set as infoprovider only.
Can anyone please let me know how to get only dimension table values when we use combo box.
Thanks & Regards
K.Srinivas Rao

Hi
Create one BI query with only one object in the output of the query. (In your case 0CALMONTH)
So now if when you run the query it will show values which are there in infoprovider. THen drag one form from output of this query in vc & create dropdown list on this.
Is this what you are looking for?
regards
Sandeep

Services formula value in contract release order

Hi
We have a quantity contract with services, the services contain a formula ABC to determine quantity. After selecting the service in the contract release order the full contract quantity is imported resulting in an error message.
Is there a specific user exit or other method to default the service formula values ABC to 111 after selecting the service in the contract release order?
thanks

Anyone any ideas? is there a user exit/enhancement or could a user parameter work?
Any guidance most appreciated.
Adrian

Make dimension values shown reflect other dimension filter values

I have created a cube and uses access this cube in an Excel pivot table. Is it possible to make values shown for one dimension display only the values valid, if I have selected another dimension's value that would limit the values that should
show under the first dimension? I tried linking the dimensions together with a key and that did not appear to do the trick. I also tried using dependsondimension in properties for the other dimension, but that did not work either. Is
there something I am missing that makes the cube only display the values in a dimension that apply when another dimension's value is filtered?

@Naveen - I am linking to the proper measure and am seeing the correct measure values.
@KR Jurgen - I'm not finding a spot to set the scope to NULL. I would, but some people need all the values.
Here's an example. I have company 1 and 2. Company 1 has item A and Company 2 has item B. They both have sales of $1. There is a company dimension and item dimension. When I filter by company 1, I see sales of $1.
The problem is, when I select the list of items from the item dimension, I still see item B. If I put the items in the row, I only see item A. The ideal situation would be to have only item A show when I select the list of items from the item
dimension. Is there some way to accomplish this?
Thank you both for your responses.

Dimension formula values

Similar Messages

Maybe you are looking for