Formula in a dimension

I have several accounts in the account dimension. I want to insert a formula in a few.
For example:
6220000 = 6210000 + 6200000
The three are dimension's members
Can i use the formula column in the maintain dimensions?
How can i do easy formulas?
Can i mix members from different levels of hierarchies?
Thanx in advance and sorry for so many questions?

Ola Jose
Yes you can use the formula column in the account dimension, even if it is not advised!!
It is not advised because it is slower than running Business Rules or logic for example... it depends if you need to make long and many calculations...
If it is only one or 2 you could do it using the Formula column
If you wanna use the Formula column then you will write MDX formulas...
here is an example of the syntax :
'([A30210],[NO_F])([A30220],[NO_F])
(i am using NO_F has a flow in this example but you can do it without flows...
or formulas like
'+Iif([A36021]<0,0,[A36021])
Otherwise I would STRONGLY advise you to use the Business Rules.
So open a business rules Account transformation and put
group    |   source account |   source flow |   dest acct   |     dest flow
Test     |      6210000         |                      |    6220000   |
Test     |      6220000         |                      |    6220000   |
and leave the other stuffs blanks...
Create a logic and add this line :
*RUN_STORED_PROCEDURE=SPRUNCALCACCOUNT([%APP%], [%Category_Set%], [LC], [%SCOPETABLE%], [%LOGTABLE%],[Test])
*Commit
Save and Validate the logic...
Test it
Business Rules are probably easier to use in your case... no?
Concerning the last question, I would advise not to mix members from different level of hierearchies because using basmembers should be faster. Parents are calculated in the cube so please stick to parents if you can...
Make a test in running parents and basemembers to see if in your case there is a big differences, but please try to stick to basmembers ...
I hope I have answered your question
Do not hesitate to ask ...
Nic

Similar Messages

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

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

Formulas in account dimension with multiple hierarchies

Hello all,
I am having troubles with finding the exact syntax for a formula in an account dimension that has two hierarchies:
- I have two parent accounts in H1 (accountA and accountB)
- I have one account in H2 that has to add up accountA and accountB
It was easy in V4, the formula would just say: accountA+accountB
Does anyone have the exact syntax for me in V5?
Some extra info:
- SAP BPC version: 5.1sp2
- SQL 2005
- I know that dimension formulas have a problem with performance, but believe me, in this case this, it is the only way
Hope someone can help me,
Alwin

Alwin,
There should be formulas in the MDXlib.lgl that look like the following examples:
*Function Hir1_P(%Arg%)
     iif(AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%, rollupchildren(AccountL.H1.currentMember,"+"))
*endfunction
*Function Hir2_P(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%, rollupchildren(AccountL.H2.currentMember,"+"))
*endfunction
*Function Hir3_P(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2],%Arg%, rollupchildren(AccountL.H3.currentMember,"+"))
*endfunction
*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
These are functions that may be used to aggregate the values in version 5 across hierarchies. I don't think you need them all, but I included the set I have in a current application.
I hope this helps.
Petar

BPC 7.5 Formula Dimension Processing Error

Hello
We have upgraded from 70-7.5 and when I do a Process of one of our dimensions i get the following error:-
- [DATASOURCE].[#Y_YROVERYR] Parser: The following syntax error occurred during parsing: Invalid token, Line 1, Offset 92, [TOTWITHA.
This is the formula in the dimension file :-
'iif(([YTD], [TotWithAlloc], ParallelPeriod(Year)) <> 0, (([YTD], [TotWithAlloc]) / ([YTD], [TotWithAlloc], ParallelPeriod(Year))) - 1, Null)
Any help please?
Rgds
Perven

Hi,
Is TOTWITHALLOC a member of the datasource dimension? Can you please quantify it completele by
[DATASRC].[TOTWITHALLOC]
Let me know if it works or not.

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

How to use Solve Order in Dimension level formula

Hi All,
Can anyone explain me how to use "Solve order" in formulas defined in dimension?
Regards,
Kapil

Hi,
Let us consider the following:
There are 3 members in your account dimension, Amt, Rate, and Prod. The data looks like
               Jan     Feb     Mar     Apr     May
Amt        100     10       20       30       40
Rate       10       20       10       20       30
Prod       1000 200     200      600     1200
The above values of the Prod will be displayed if the measure in CV is set to periodic. However, if you change the measure in CV to YTD and change the time dimension to dec, then you should get the below result.
              Dec
Amt       200
Rate      90
Prod      3200
This value is nothing but the total of the entire year.
Hope this helps.

BPC NW 10 Member formula

Hello Experts,
I have a BPC NW 10 requirement to calculate member formula for Account Dimension.
SALES_TTM(Total Sales - 12months Trailing) which is SALESTOT+(SALESTOT, Prior Period)+(SALESTOT, Prior Period 2)+(SALESTOT, Prior Period 3)+(SALESTOT, Prior Period 4)+(SALESTOT, Prior Period 5)+(SALESTOT, Prior Period 6)+(SALESTOT, Prior Period 7)+(SALESTOT, Prior Period 8)+(SALESTOT, Prior Period 9)+(SALESTOT, Prior Period 10)+(SALESTOT, Prior Period 11).
SALESTOT member is not a Base Member.Its a node which has several Base members in it.
How Can I write a Member Formula for the above requirement?
Thanks

Hello Vadim,
I was able to write the formula and test it properly using LAG functionality for time,
I have a similar requirement for YTD model and posted it in a seperate post.I have written a formula but couldnt make it dynamic to make it work for all years
Can you please help?
Below is the link
http://scn.sap.com/thread/3607494
Thanks

Creating alias for BEx dimensions in crystalreport

I need help with creating alias formula for BEx dimensions in crystal report. Iam trying to follow the book, but i don't know what should be the result.

Hi,
Crystal Reports is using the technical names of the InfoObjects itself so those names should be familiar assuming you also know the BEx Query.
If you want to create some form of an alias the option I can see is to create a set of formulas which simply include the field and then use those formulas as part of any other formulas.
regards
Ingo Hilgefort

Processing a dimension error message failed to expand K2 function

Hi SAP gurus,
For doing processing of a dimension i am getting the error message,
Failed to expand k2 funtion for dimension P_ACCT'S member formulas
Members invalid On Dimensin (RPTCURRENCY:LC)
The error message is only when i am using FORMULA in a dimension, with out FORMULA its processing successful.
I checked with the development environment its working fine even i use FORMULA. But in production its giving the above error message.
How to Resolve the issue in production server.
Thanks & Regards
Swathi Roy

Hi,
Please do the following on BPC Server:
1). unregister the following dlls :
K2processing.dll, K2processingInternal.dll and K2Logic.dll
All the above files will be in C:\.. \BPC\Websrvr\bin
(Folders)
you have to un each dll saparately at DOS prompt.
regsvr32 /u C:\BPC\Websrvr\bin\k2logic.dll
2). re-register the same dlls :
(K2processing.dll, K2processingInternal.dll and K2Logic.dll)
Running the DOS command for each dll
- The dlls are located in C:\BPC\Websrvr\bin folder
regsvr32 C:\BPC\Websrvr\bin\K2Logic.dll
I hope this helps
I unregistered the K2processingInternal.dll and then register again, but the problem was not resolved.
and i am not able to find K2processing.dll, K2Logic.dll in both production and development servers.
in development server also we cant find the above dll files, but its working fine in dev server
The problem is in production server only if i use FORMULA.
please help me to over come the issues
Thanks & Regards
Swathi Roy

Pbm to display a formula in multi Writer mode

hello,
I attach my analytic workspace in multi write mode and when i want to display a formula in a crosstab, i have the following message :
on Jan 17 16:22:30 CET 2005 In oracle.dss.dataSource.QueryServer::_restartFromPersistence
oracle.express.ExpressServerExceptionClasse d'erreurs : OLAPI
Descriptions des erreurs du serveur :
DPR : Unable to create server cursor, GÃ©nÃ©rique Ã TxsOqDefinitionManagerSince9202::crtCurMgrs2
OES : ORA-37035: You can only DEFINE SESSION objects in analytic workspace EISEVAL because it is attached in MULTI mode.
, GÃ©nÃ©rique Ã TxsRdbResultSet:absolute()
     at oracle.express.olapi.data.full.DefinitionManager$ExceptionTranslator.translateExpressException(DefinitionManager.java:571)
     at oracle.express.olapi.data.full.DefinitionManager$ExceptionTranslator.translateException(DefinitionManager.java:551)
     at oracle.express.olapi.data.full.DefinitionManager.translateException(DefinitionManager.java:513)
     at oracle.express.olapi.data.full.DefinitionManager.translateException(DefinitionManager.java:520)
     at oracle.express.olapi.data.full.DefinitionManagerSince9202.createCursorManagerInterfaces(DefinitionManagerSince9202.java:522)
     at oracle.express.olapi.data.full.DefinitionManagerSince9202.createOLAPICursorManagers(DefinitionManagerSince9202.java:891)
     at oracle.express.olapi.data.full.ExpressDataProvider.createCursorManagers(ExpressDataProvider.java:1671)
     at oracle.express.olapi.data.full.ExpressDataProvider.internalCreateCursorManager(ExpressDataProvider.java:770)
     at oracle.express.olapi.data.full.ExpressDataProvider.createCursorManager(ExpressDataProvider.java:708)
     at oracle.olapi.data.source.DataProvider.createCursorManager(DataProvider.java:330)
     at oracle.olapi.data.source.DataProvider.createCursorManager(DataProvider.java:273)
     at oracle.dss.dataSource.QueryCursorManager.createCursorManager(QueryCursorManager.java:164)
     at oracle.dss.dataSource.QueryEvaluator.setUpCursors(QueryEvaluator.java:3546)
     at oracle.dss.dataSource.QueryEvaluator._setUpCursorsForMainQuery(QueryEvaluator.java:2547)
     at oracle.dss.dataSource.QueryEvaluator.getCursorForCube(QueryEvaluator.java:2579)
     at oracle.dss.dataSource.QueryEvaluator.createCubeAndCursor(QueryEvaluator.java:940)
     at oracle.dss.dataSource.MainQueryEvaluator.createCubeAndCursor(MainQueryEvaluator.java:144)
     at oracle.dss.dataSource.QueryServer.createCubeAndCursor(QueryServer.java:3698)
     at oracle.dss.dataSource.QueryServer._restartFromPersistence(QueryServer.java:6297)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java)
     at oracle.dss.util.Operation.execute(Operation.java:72)
     at oracle.dss.dataSource.QueryManagerServer.sendQueue(QueryManagerServer.java:1991)
     at oracle.dss.dataSource.common.OperationQueue.update(OperationQueue.java:207)
     at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
     at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
     at oracle.dss.dataSource.client.QueryClient._databaseSet(QueryClient.java:3888)
     at oracle.dss.dataSource.client.QueryClient._reestablishFromPersistence(QueryClient.java:349)
     at oracle.dss.dataSource.client.QueryClient.setXMLAsString(QueryClient.java:518)
     at oracle.dss.persistence.persistencemanager.client.DefaultStateHandler.loadXML(DefaultStateHandler.java:131)
     at oracle.dss.persistence.persistencemanager.client.DefaultStateHandler.recreatePersistableFromStateAgent(DefaultStateHandler.java:395)
     at oracle.dss.metadataManager.client.handlers.persistence.PersistenceMetadataHandler$MDStateHandler.recreatePersistableFromStateAgent(PersistenceMetadataHandler.java:491)
     at oracle.dss.persistence.persistencemanager.client.DefaultStateHandler.loadAggregates(DefaultStateHandler.java:257)
     at oracle.dss.persistence.persistencemanager.client.DefaultStateHandler.recreatePersistableFromStateAgent(DefaultStateHandler.java:401)
     at oracle.dss.metadataManager.client.handlers.persistence.PersistenceMetadataHandler$MDStateHandler.recreatePersistableFromStateAgent(PersistenceMetadataHandler.java:491)
     at oracle.dss.metadataManager.client.handlers.persistence.PersistenceMetadataHandler.getObjectInstance(PersistenceMetadataHandler.java:669)
     at oracle.dss.metadataManager.client.MetadataManager.handleStateAgent(MetadataManager.java:6336)
     at oracle.dss.metadataManager.client.MetadataManager.lookup(MetadataManager.java:5966)
     at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:378)
     at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:258)
     at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:254)
     at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:550)
Is there a workaround ?
Thanks

hello,
My formula come from an express Server database 6.3.4.
I have made a simple test case: The Express Database contains only 2 formulas
with 2 dimensions. I export it , create an aw in the CS_OLAP schema and import the eif file by AWM 10.1.0.3.0
and enable to standard form.
I ran the bicheckconfig and apparently no problem :
<?xml version="1.0" encoding="UTF-8" ?>
<BICheckConfig version="1.0.2.0">
<Check key="JDEV_ORACLE_HOME" value="G:\oracle\product\10.1.0\Dev"/>
<Check key="JAVA_HOME" value="G:\oracle\product\10.1.0\Dev\jdk\jre"/>
<Check key="JDeveloper version" value="10.1.2.0.0.1811"/>
<Check key="BI Beans release description" value="BI Beans 10.1.2 Production Release"/>
<Check key="BI Beans component number" value="10.1.2.52.0"/>
<Check key="BI Beans internal version" value="3.2.1.0.13"/>
<Check key="host" value="dev2"/>
<Check key="port" value="1521"/>
<Check key="sid" value="orc10G"/>
<Check key="user" value="cs_olap"/>
<Check key="Connecting to the database" value="Successful"/>
<Check key="JDBC driver version" value="10.1.0.3.0"/>
<Check key="JDBC JAR file location" value="G:\oracle\product\10.1.0\Dev\jdbc\lib"/>
<Check key="Database version" value="10.1.0.3.0"/>
<Check key="OLAP Catalog version" value="10.1.0.3.0"/>
<Check key="OLAP AW Engine version" value="10.1.0.2.0"/>
<Check key="OLAP API Server version" value="10.1.0.3.0"/>
<Check key="BI Beans Catalog version" value="3.2.1.0.13"/>
<Check key="OLAP API JAR file version" value=""10.1.0.3.0""/>
<Check key="OLAP API JAR file location" value="G:\oracle\product\10.1.0\Dev\jdev\lib\ext"/>
<Check key="OLAP API Metadata Load" value="Successful"/>
<Check key="Number of metadata folders" value="4"/>
<Check key="Number of metadata measures" value="26"/>
<Check key="Number of metadata dimensions" value="7"/>
<Check key="OLAP API Metadata">
<![CDATA[==============================================================================
Type Name (S=Schema, C=Cube, M=Measure, D=Dimension) Status
========= ======================================================= ============
Folder... ROOT
Measure.. Nombre de Jours par mois Successful
S=CS_OLAP, C=NBJ_MOIS_CUBE4151, M=NBJ_MOIS
Measure.. Formule Xdimension Successful
S=CS_OLAP, C=FULE_XDIMENSION_CUBE4151, M=FULE_XDIMENSION
Dimension Temps Successful
S=CS_OLAP, D=EISEVAL_TEMPS
Dimension Dimensions Successful
S=CS_OLAP, D=EISEVAL_XDIMENSION
Folder... Electronics - KPIs
Measure.. Revenue Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD
Measure.. Cost Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS
Measure.. Quantity Successful
S=CS_OLAP, C=SHAWSALES, M=QUANTITY_SOLD
Dimension Time Successful
S=CS_OLAP, D=SHAWT_TIME
Dimension Promotion Successful
S=CS_OLAP, D=SHAWPROMOTIONS
Dimension Product Successful
S=CS_OLAP, D=SHAWPRODUCTS
Dimension Geography Successful
S=CS_OLAP, D=SHAWGEOGRAPHIES
Dimension Channel Successful
S=CS_OLAP, D=SHAWCHANNELS
Folder... Electronics - Trend Calculations
Measure.. Revenue Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD
Measure.. Revenue 12 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_12MMA
Measure.. Revenue 6 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_6MMA
Measure.. Revenue Fcst Best Fit Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_BF
Measure.. Revenue Fcst Exponential Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_EXPO
Measure.. Revenue Fcst Linear Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_LINEAR
Measure.. Revenue Fcst Non-Linear Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_NLINEAR
Measure.. Revenue Fcst Seasonal Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_SEASONAL
Measure.. Revenue Fcst Trend Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_TREND
Measure.. Revenue % Growth Prior Period Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_PCT_CHANGE_PP
Measure.. Revenue % Growth Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_PCT_CHANGE_YRAGO
Measure.. Cost Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS
Measure.. Cost 12 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS_12MMA
Measure.. Cost 6 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS_6MMA
Measure.. Cost Fcst Best Fit Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS_FCAST_BF
Measure.. Cost % Growth Prior Period Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS_PCT_CHANGE_PP
Measure.. Cost % Growth Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS_PCT_CHANGE_YRAGO
Measure.. Margin 12 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_12MMA
Measure.. Margin 6 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_6MMA
Measure.. Margin Fcst Best Fit Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_FCAST_BF
Measure.. Margin % Growth Prior Period Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_PCT_CHANGE_PP
Measure.. Margin % Growth Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_PCT_CHANGE_YRAGO
Measure.. Margin % Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_PERCENT
Measure.. Quantity Successful
S=CS_OLAP, C=SHAWSALES, M=QUANTITY_SOLD
Dimension Time Successful
S=CS_OLAP, D=SHAWT_TIME
Dimension Promotion Successful
S=CS_OLAP, D=SHAWPROMOTIONS
Dimension Product Successful
S=CS_OLAP, D=SHAWPRODUCTS
Dimension Geography Successful
S=CS_OLAP, D=SHAWGEOGRAPHIES
Dimension Channel Successful
S=CS_OLAP, D=SHAWCHANNELS
Folder... Electronics - Trend Calculations
Measure.. Quantity Successful
S=CS_OLAP, C=SHAWSALES, M=QUANTITY_SOLD
Measure.. Margin % Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_PERCENT
Measure.. Margin % Growth Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_PCT_CHANGE_YRAGO
Measure.. Margin Fcst Best Fit Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_FCAST_BF
Measure.. Margin 12 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_12MMA
Measure.. Cost % Growth Prior Period Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS_PCT_CHANGE_PP
Measure.. Cost 6 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS_6MMA
Measure.. Cost 12 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS_12MMA
Measure.. Revenue % Growth Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_PCT_CHANGE_YRAGO
Measure.. Revenue 12 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_12MMA
Measure.. Revenue 6 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_6MMA
Measure.. Revenue Fcst Best Fit Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_BF
Measure.. Revenue Fcst Exponential Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_EXPO
Measure.. Revenue Fcst Linear Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_LINEAR
Measure.. Revenue Fcst Non-Linear Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_NLINEAR
Measure.. Revenue Fcst Seasonal Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_SEASONAL
Measure.. Revenue Fcst Trend Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_FCAST_TREND
Measure.. Revenue % Growth Prior Period Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD_PCT_CHANGE_PP
Measure.. Revenue Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD
Measure.. Cost Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS
Measure.. Cost Fcst Best Fit Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS_FCAST_BF
Measure.. Cost % Growth Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS_PCT_CHANGE_YRAGO
Measure.. Margin 6 Mo MV Avg Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_6MMA
Measure.. Margin % Growth Prior Period Successful
S=CS_OLAP, C=SHAWSALES, M=MARGIN_PCT_CHANGE_PP
Dimension Time Successful
S=CS_OLAP, D=SHAWT_TIME
Dimension Promotion Successful
S=CS_OLAP, D=SHAWPROMOTIONS
Dimension Product Successful
S=CS_OLAP, D=SHAWPRODUCTS
Dimension Geography Successful
S=CS_OLAP, D=SHAWGEOGRAPHIES
Dimension Channel Successful
S=CS_OLAP, D=SHAWCHANNELS
Folder... Electronics - KPIs
Measure.. Quantity Successful
S=CS_OLAP, C=SHAWSALES, M=QUANTITY_SOLD
Measure.. Revenue Successful
S=CS_OLAP, C=SHAWSALES, M=AMOUNT_SOLD
Measure.. Cost Successful
S=CS_OLAP, C=SHAWSALES, M=COSTS
Dimension Time Successful
S=CS_OLAP, D=SHAWT_TIME
Dimension Promotion Successful
S=CS_OLAP, D=SHAWPROMOTIONS
Dimension Product Successful
S=CS_OLAP, D=SHAWPRODUCTS
Dimension Geography Successful
S=CS_OLAP, D=SHAWGEOGRAPHIES
Dimension Channel Successful
S=CS_OLAP, D=SHAWCHANNELS
]]>
</Check>
</BICheckConfig>
The formula has the following description :
DEFINE NBJ_MOIS FORMULA INTEGER <TEMPS>
LD Nombre de Jours par mois
EQ 1
PROPERTY 'AW$CLASS' -
'IMPLEMENTATION'
PROPERTY 'AW$CREATEDBY' -
'AW$XML'
PROPERTY 'AW$LASTMODIFIED' -
'24JAN05_17:05:22'
PROPERTY 'AW$LOGICAL_NAME' -
'NBJ_MOIS'
PROPERTY 'AW$MEASUREDEF' NA
PROPERTY 'AW$PARENT_NAME' -
'NBJ_MOIS_CUBE4151'
PROPERTY 'AW$ROLE' -
'MEASUREDEF'
PROPERTY 'AW$STATE' -
'VALID_MEMBER'
PROPERTY 'COLUMN_NAME' -
'MEASURE_19'
PROPERTY 'CURRSYMBOL' -
'Â¿'
PROPERTY 'DATA_TYPE' -
'INTEGER'
PROPERTY 'DECIMALDIGITS' 2
PROPERTY 'DESCRIPTION' -
'Nombre de Jours par mois'
PROPERTY 'DISPLAYNAME' -
'Nombre de Jours par mois'
PROPERTY 'FORMATNEGCURR' -
'($1)'
PROPERTY 'FORMATNEGNUM' -
'(Â¿1)'
PROPERTY 'FORMATPOSCURR' -
'$1'
PROPERTY 'FORMATPOSNUM' -
'Â¿1'
PROPERTY 'ISCURRENCY' non
PROPERTY 'IS_SOLVETARGET' oui
PROPERTY 'LONGNAME' -
'Nombre de Jours par mois'
PROPERTY 'NAME' -
'NBJ_MOIS'
PROPERTY 'NUMFORMAT' -
'0.00;Â¿1;(Â¿1);;,=;;'
PROPERTY 'SHORTNAME' -
'Nombre de Jours par mois'
PROPERTY 'SHOWLEADZERO' oui
PROPERTY 'USERDATA' oui
PROPERTY 'USETHOUSANDSEP' non
In the sample JAVA bibeans 10G "adhoc_tool"
I insert just one line to reproduce the problem
AnalyzerConnection.java
protected void connect() {
m_queryManager.setSession(m_session);
m_queryManager.setMetadataManager(m_metadataManager);
m_connected = true;
// Save the connection details
saveConnectionSettings();
System.out.println(olapCon.executeCommand("aw attach EISEVAL multi;aw list")); <------------this line
catch (Exception e) {
// The _mm.attach method call can fail if the user - who is a valid
// database user, is not a valid catalog user
showConnectionError(e);
and when i choose my fomula for a new presentation i have the following error :
Mon Jan 24 19:21:43 CET 2005 In BuilderWizardAdapter::wizardFinished
BIB-9509 Oracle OLAP n'a pas crÃ©Ã© le curseur.
oracle.express.ExpressServerExceptionClasse d'erreurs : OLAPI
Descriptions des erreurs du serveur :
DPR : Unable to create server cursor, GÃ©nÃ©rique Ã TxsOqDefinitionManagerSince9202::crtCurMgrs2
OES : ORA-37035: You can only DEFINE SESSION objects in analytic workspace EISEVAL because it is attached in MULTI mode.
, GÃ©nÃ©rique Ã TxsRdbResultSet:absolute()......
If i attach in RO mode , it works.
jean marc

Error when processing dimensions

Hello,
I'm working with BPC 7.0 NW and I'm trying to process the dimension P_ACC (copied from the APSHELL directly) and I get the following errors:
"Failed to expand K2 function for dimension P_ACCT's member formulas" and
"MDX statement error:"You do not have the authorization for component !!"
Any idea about how to solve this erros?
Thanks and regards,
Ana

Hi Ana
Its called MDXLib.lgl not MDX.lgl
find that in the appset apshell and try to copy the same in similar path in your appset.
I think it must be in logic files folder not sure of exact path.
But that should not be issue here since you are using direct MDX Query, can you just remove that one formula and process dimension and then remove the cache
Then add back the formula and then see how it works, then try using some other account for now as divisor (Denominator) and see what happens
Thanks and Regards
Harish B K

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

Account formula concatenate

Hi,
I am writing because I need to know how to make the following formula work:
In the formula of account dimension:
How can I concatenate the property YEAR of the dimension Time?
.[10101],[Entity].[Risk],[Time].currentmember.Properties("YEAR").[JAN]
What I mean is that I take the current member's year (i.e: 2009.MAR--> ) and then, I concatenate its year with .JAN, so that I can always calculate the first month in course.
I don't want to send dates with this account, it´s just for reports.
Edited by: Leon Francisco on Sep 3, 2009 12:38 PM
Edited by: Leon Francisco on Sep 3, 2009 12:39 PM

Hi again Leon,
Thanks for this reply. I'm encountering the same problem when I try to do this on my environment. Anyway, I can drive you to other potential solutions.
- First, I know that you can use "StringToMember" formula call in a dimension formula for such error messages when processing. I know this is quite hard to implement this, but this could be a first potential solution. But be aware of performance problem building so complicated formulas in that case.
- Secondly, you could only have your dimension formula set to "[Account].[100010],[Entity].[Risk]" for your "NewAccount" member and then reference the right time period directly in the report. I mean, you can use EVCVW formula to reference the actual Time member, and then use EVPRO function in another cell that will reference this and retrieve "year" property (for example in cell D1). Then, just build an EVGET function like this:
EVGET(AppName, "NewAccount", D1&".JAN",..........)
- Third solution, instead of having only one account called "NewAccount" with a complicated dimension formula (which can of course impact performance, too), you could have for example one "NewAccount" per year. I mean:
NewAccount2006 (dimension formula: "[Account].[100010],[Entity].[Risk],[Time].[2006.JAN]"
NewAccount2007 (dimension formula: "[Account].[100010],[Entity].[Risk],[Time].[2007.JAN]"
NewAccount2008 (dimension formula: "[Account].[100010],[Entity].[Risk],[Time].[2008.JAN]".....
And then you can use some basic Excel function in order to check the actual Year in CV, and retrieve the right dependant "NewAccount".
I hope this will help you.
Kind Regards,
Patricki

Webi report looses merge dimension and block filter during Universe Change

Hi All,
I have come across a weird behavior in BOXI 3.1 SP3. Please find below the details for the same:
1. I have a report which has a varible built on formula using a merged dimension.
2. When i migrate the report from development to acceptance environment and change the universe from report properties, formula using merged dimension object gets corrupt.
3. Same issue is available with block level filter also.
Please let me know if there is a solution for this and this looks to be a bug in the BOXI tool.
Please let me know if I need to provide additional details.
Regards,
Chetan Dodiya
Edited by: Chetanin on Dec 19, 2011 3:13 PM

Greetings,
I am not sure what you mean by changing the universe from report properties. Do you mean that you edit the report and go to the Query Panel and change the universe from there?
If this is your workflow, then this is not a product defect. You will have to revalidate your formulas. As the Merged dimensions will be recreated.
Normally when migrating from one test to dev and dev to Prod, the only change should be the connection that points to the correct database. The connection of your universe should be the only thing that change.
Please note that the connection name remane the same. But you edit the connection and change the database to which your universe is pointing to.
Provided that the tables name and columns name are identical between your different environment, there should not be any issue.

Formula in a dimension

Similar Messages

Maybe you are looking for