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.

Similar Messages

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

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

Error in Dimension Formula

Hi,
There are dimension formulas maintained in my Account dimension. When I am processign the dimension, the processing is failing telling that for few of the members, the formula is getting in to an infinite recursion. I have checked the code a lot of times. However, unable to understand why this error is coming.
The formula for one of the dimension members looks like this
((Account.H2.PL332000+Account.H2.PL331000)/(val([Time].properties("Monthnum"))/12))/
([Account.H1].[FTE_R_D],[ACCDETAIL].[FTE_TOT]),SOLVE_ORDER=50
Kindly help me.

Thanks Sorin for the response.
In that case, what can be the solution?
I have seen examples in which members from different tables, like accdetail, are used in the formulas. They are working absolutely fine.
My understanding says that the different hierarchies are stored in different tables. So, hierarchy 1 will be stored in the table Account.H1 and hierarchy 2 will be stored in Account.H2.
If, we are able to use members which is present in accdetail table, ideally we should be able to use the members which are present in Account.H2 as well. Its just the table from where we are fetching the members.
Kindly help me if I am wrong in my concept

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

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

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

SSRS 2008 Column Chart with Calculated Series (moving average) "formula error - there are not enough data points for the period" error

I have a simple column chart grouping on 1 value on the category axis. For simplicity's sake, we are plotting $ amounts grouping by Month on the category axis. I right click on the data series and choose "Add calculated series...". I choose moving average. I want to move the average over at least 2 periods.
When I run the report, I get the error "Formula error - there are not enough data points for the period". The way the report is, I never have a guaranteed number of categories (there could be one or there could be 5). When there is 2 or more, the chart renders fine, however, when there is only 1 value, instead of suppressing the moving average line, I get that error and the chart shows nothing.
I don't think this is entirely acceptable for our end users. At a minimum, I would think the moving average line would be suppressed instead of hiding the entire chart. Does anyone know of any workarounds or do I have to enter another ms. connect bug/design consideration.
Thank you,
Dan

I was having the same error while trying to plot a moving average across 7 days. The work around I found was rather simple.
If you right click your report in the solution explorer and select "View Code" it will give you the underlying XML of the report. Find the entry for the value of your calculated series and enter a formula to dynamically create your periods.
<ChartFormulaParameter Name="Period">
<Value>=IIf(Count(Fields!Calls.Value) >= 7 ,7, (Count(Fields!Calls.Value)))</Value>
</ChartFormulaParameter>
What I'm doing here is getting the row count of records returned in the chart. If the returned rows are greater than or equal to 7 (The amount of days I want the average) it will set the points to 7. If not, it will set the number to the amount of returned rows. So far this has worked great. I'm probably going to add more code to handle no records returned although in my case that shouldn't happen but, you never know.
A side note:
If you open the calculated series properties in the designer, you will notice the number of periods is set to "0". If you change this it will overwrite your custom formula in the XML.

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

Changing database server on a report with subreports = formula error

Good morning,
I currently have several reports that print out, and were developed attached to our development database. However, I need to be able to dynamically change the server that the report uses according to the server configured in our application. Each of these reports contains one or more subreports, which point to the same server and database as the main report. All reports, both the main and subreports, are based on manual SQL commands.
I'm running into some significant issues. So significant, in fact, that we were forced to deploy our application with reports that had been switched to our production environment in the designer in order to get them functional. This is, obviously, not an acceptable or long-term solution.
I've gone round and round a couple of times I get different results with different methods of changing this information. I'll outline them below. First, my current code:
ConnectionInfo connectionInfo = new ConnectionInfo();
                TableLogOnInfo logOnInfo = new TableLogOnInfo();
                Console.WriteLine("Report \"{0}\"", report.Name);
                foreach (Table table in report.Database.Tables)
                    logOnInfo = table.LogOnInfo;
                    connectionInfo = new ConnectionInfo(logOnInfo.ConnectionInfo);
                    connectionInfo.ServerName = "panthers-dev";
                    connectionInfo.DatabaseName = "Prosys";
                    logOnInfo.ConnectionInfo = connectionInfo;
                    //table.Location = "Prosys.dbo." + table.Location.Substring(table.Location.LastIndexOf(".") + 1);
                    table.ApplyLogOnInfo(logOnInfo);
                    table.LogOnInfo.ConnectionInfo = connectionInfo;
                    Console.WriteLine("\t\"{0}\": \"{1}\", \"{2}\", \"{3}\", {4}", table.Name, table.LogOnInfo.ConnectionInfo.ServerName, table.LogOnInfo.ConnectionInfo.DatabaseName, table.Location, table.TestConnectivity());
                foreach (Section section in report.ReportDefinition.Sections)
                    foreach (ReportObject ro in section.ReportObjects)
                        if (ro.Kind == ReportObjectKind.SubreportObject)
                            SubreportObject sro = (SubreportObject)ro;
                            ReportDocument subreport = report.OpenSubreport(sro.SubreportName);
                            Console.WriteLine("\tSubreport \"{0}\"", subreport.Name);
                            foreach (Table table in subreport.Database.Tables)
                                logOnInfo = table.LogOnInfo;
                                connectionInfo = new ConnectionInfo(logOnInfo.ConnectionInfo);
                                connectionInfo.ServerName = "panthers-dev";
                                connectionInfo.DatabaseName = "Prosys";
                                logOnInfo.ConnectionInfo = connectionInfo;
                                //table.Location = "Prosys.dbo." + table.Location.Substring(table.Location.LastIndexOf(".") + 1);
                                table.ApplyLogOnInfo(logOnInfo);
                                table.LogOnInfo.ConnectionInfo = connectionInfo;
                                Console.WriteLine("\t\t\"{0}\": \"{1}\", \"{2}\", \"{3}\", {4}", table.Name, table.LogOnInfo.ConnectionInfo.ServerName, table.LogOnInfo.ConnectionInfo.DatabaseName, table.Location, table.TestConnectivity());
Using this approach, my console output prints what I expect and want to see: the correct server and database information, and True for TestConnectivity for all reports and subreports. The two reports I have that have no subreports print out correctly, with data from the proper server. However, all of the reports with subreports fail with formula errors. If this procedure is not run, they work just fine on either server.
I had to place the assignment of table.LogOnInfo.ConnectionInfo = connectionInfo after the call to ApplyLogOnInfo, as that function did not behave as expected. If I perform the assignment first (or not at all), then calling ApplyLogOnInfo on the outer report's table did NOT affect the values of its ConnectionInfo object, but it DID affect the values of the ConnectionInfo object's of its subreports!
In any event, if anyone could post a code sample of changing database connection information on a report containing subreports, I would appreciate it.
Any help is greatly appreciated and anxiously awaited!

Hi Adam,
Code for changing database connection information on a report containing subreports :
private ReportDocument northwindCustomersReport;
    private void ConfigureCrystalReports()
        northwindCustomersReport = new ReportDocument();
        string reportPath = Server.MapPath("NorthwindCustomers.rpt");
        northwindCustomersReport.Load(reportPath);
        ConnectionInfo connectionInfo = new ConnectionInfo();
        connectionInfo.ServerName = "localhost";
        connectionInfo.DatabaseName = "Northwind";
        connectionInfo.IntegratedSecurity = false;
        SetDBLogonForReport(connectionInfo, northwindCustomersReport);
        SetDBLogonForSubreports(connectionInfo, northwindCustomersReport);
        crystalReportViewer.ReportSource = northwindCustomersReport;
    private void Page_Init(object sender, EventArgs e)
        ConfigureCrystalReports();
    private void SetDBLogonForReport(ConnectionInfo connectionInfo, ReportDocument reportDocument)
        Tables tables = reportDocument.Database.Tables;
        foreach (CrystalDecisions.CrystalReports.Engine.Table table in tables)
            TableLogOnInfo tableLogonInfo = table.LogOnInfo;
            tableLogonInfo.ConnectionInfo = connectionInfo;
            table.ApplyLogOnInfo(tableLogonInfo);
    private void SetDBLogonForSubreports(ConnectionInfo connectionInfo, ReportDocument reportDocument)
        Sections sections = reportDocument.ReportDefinition.Sections;
        foreach (Section section in sections)
            ReportObjects reportObjects = section.ReportObjects;
            foreach (ReportObject reportObject in reportObjects)
                if (reportObject.Kind == ReportObjectKind.SubreportObject)
                    SubreportObject subreportObject = (SubreportObject)reportObject;
                    ReportDocument subReportDocument = subreportObject.OpenSubreport(subreportObject.SubreportName);
                    SetDBLogonForReport(connectionInfo, subReportDocument);
Hope this helps!!
Regards,
Shweta

Getting "Unexpected end of formula" error in user-defined function

I created a user-defined function and registered it successfully in Discoverer Admin (10g), and it shows up in Discoverer Plus. However, when I call the function, I get this error:
"Error in formula -- unexpected end of formula"
If I hard-code in parameters, I can successfully run the function as such from Oracle SQL Developer:
SELECT PAYLINETOT('2324', '111', to_date('01-Sep-2010'), to_date('31-Oct-2010'))
FROM DUAL;
But I still get the same error if I enter this in the calculation dialog in Discoverer:
PAYLINETOT('2324', '111', to_date('01-Sep-2010'), to_date('31-Oct-2010'))
Any idea what's going on and how to get this to work?

Michael,
I tried your suggestion, and this time I got a different error message that said that the function had not been registered with the EUL. I thought I had registered it, but when I checked, the return data type was wrong. I corrected it, and the function is "valid" in Discoverer Admin. Yet, when I go back to Discoverer Plus and attempt to use the function (and yes, I logged out and logged back in), I get the same error message:
"Error in formula - unexpected end of formula - Error: Function PAYLINETOT has not been registered with the EUL."
Any idea where the disconnect is? Are these two separate errors? How could Discoverer Admin tell me that the function is registered and Discoverer Plus tell me otherwise? And yes, I've made sure that the "Available in Desktop/Plus" checkbox is checked.

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

BI Integrated Planning - Formula - Formula error: } expected

Hi
BI Integrated Planning -
While defining the Formula (FOX), we are getting the below error
'Formula error: } expected'
Kindly inform if any one has faced the similar problem / any solution
Thanks in advance
G K Mohata

Giriraj,
This seems like a syntax error in your formula. It must be specifying a line number where it is finding the error. Please check that or maybe the previous line, for any data processing statement where you missed a <b>}</b>. Could be that you missed in a statement, one or more characteristics. If you cant find it, please paste your whole code here along with complete error message.
Hope this helps.

Dimension formula

I am copying the dimension formula from BPC5.1 to 7.0.
However following dimension forumula does not work in BPC7 when copied as it is.
ACCOUNT3 = -PrevBalance(ACCOUNT4)
ACCOUNT3 is the dimension member "which stores the previous month balance of Account 4.
I am surpraised why the formula which used to work in 5.1 does not work in 7
Can someone tell me what is wrong or give me link to know the MDX formula changes from 5.1 to 7
Any document link or reference that I can refer to..

Hi,
As Carlos specified, you can check the below lines in the OPTIONS tab of your dimension sheet.
*SYSLIB MDXLIB.LGL
*INCLUDE CONSTANTS.LGL
In addition to the above, I would request you to check few more things.
1. How many hierarchies do you have? If more than 1 hierarchy, then, are ACCOUNT3 and ACCOUNT4 are in the same hierarchy? If not, then the formula wont work. If yes, you will have to specify it as ACCOUNT.H1.ACCOUNT4.
2. Try the formula (PrevBalance(ACCOUNT4)*(-1))
Hope it helps.

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

Dimension formula error

Similar Messages

Maybe you are looking for