@ALIAS in FIX Statement

Hi,
Can I use @ALIAS function in FIX statement? When i try to do it it says "Error: 1200315 Error parsing formula for [FIX STATEMENT] (line 1): invalid object type". If not is there any work around for it?
Thanks.

Hi Glenn,
Thanks for the swift reply.
Here is my scenario, we do end of week analysis and our period dimension is as below,
2010 (~) <20> (Label Only)
2010-05-19 (~) (Alias: Week_3_May)
2010-05-12 (~) (Alias: Week_2_May)
2010-05-05 (~) (Alias: Week_1_May)
2010-04-28 (~) (Alias: Week_4_April)
2010-04-21 (~) (Alias: Week_3_April)
2010-04-14 (~) (Alias: Week_2_April)
and there is a different calculation for every week. So what I am trying to do is having a substitution variable CurrMnth with value "May" and then in the calculation use the @CONCATENATE("Week_3_",&CurrMnth) and do the endof week calculation on that member. Does that work?
If not is there any function we can pick the first member, second member etc individually under a parent?

Similar Messages

Doubt in FIX statement..

Hi Friends,
Why do we have square brackets for some members in the FIX statement, like in example below..
FIX(&CurrentProjMonth:"Dec","CURRENT",[LE],[Product],...
Thanks,
Raju..
Edited by: 988835 on Feb 18, 2013 10:14 PM

Hi,
Square brackets in business rule symbolizes those are Run Time Prompts and are global variables.
Hope this helps.
Regards
-SM

Using alias in where statement

simple sql:
SELECT EMPLOYEE_ID,
FIRST_NAME,
LAST_NAME,
EMAIL,
PHONE_NUMBER,
HIRE_DATE,
JOB_ID,
SALARY,
COMMISSION_PCT,
MANAGER_ID,
DEPARTMENT_ID
FROM EMPLOYEES
WHERE EMPLOYEE_ID > 1000;
is it somehow possible to use alias in where statement like
SELECT EMPLOYEE_ID "ID",
FIRST_NAME,
LAST_NAME,
EMAIL,
PHONE_NUMBER,
HIRE_DATE,
JOB_ID,
SALARY,
COMMISSION_PCT,
MANAGER_ID,
DEPARTMENT_ID
FROM EMPLOYEES
WHERE "ID" > 1000;

Hi,
is it somehow possible to use alias in where statement likeWhy do you need it?
To answer your question "Not directly"
SQL> select empno eno, sal
2 from emp
3 where eno = 7900;
where eno = 7900
ERROR at line 3:
ORA-00904: "ENO": invalid identifierColumn Alias are names given to give meaningful names to columns or the arithmetic operations' column.
Twinkle

Use of attributes in FIX statement w/ other mbrsets

Hi all,I just discovered that in 6.1.4, using a FIX statement like:FIX (@ATTRIBUTE("Diet"), @LEVMBRS(Products, 0))will actually select all products, not just a subset that have the attribute "Diet" (where "Diet" is, of course, an attribute of products).Now you might think I'm ignorant, since it seems logical that the subset "Diet" might be overridden by the superset "Products". However the same problem happens if I use:FIX (@ATTRIBUTE("Diet"), @ATTRIBUTE("Discontinued"))This statement returns neither the intersection nor the union of those two subsets - I seem to get ALL products.What gives? Am I just a foolish country boy?-dan

Does this select ALL of the products, or just the Level 0 products? The reason I ask is that the statement will not be combined using AND logic - only members of different dimensions will be combined using AND logic. Try the following:FIX (@LEVMBRS(Product, 0) AND @ATTRIBUTE(Diet))Now, if your attribute is at level 0 (I assume it is) and you want to select them, just use:FIX (@ATTRIBUTE(Diet))That will select all of the products that have a Diet attribute.Hope that helps.Regards,Jade-------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Using variables in a fix statement

I am using a nested fix statement on a dense member and would like to use variables to represent certain intersections. Since the variables need to be within a calc member bloc, where do I place them? Do they go inside the fix statement witht the parenthesis just around teh variables or the last parenthesis at the end of the fix statement?

If you mean substitution variables, they are defined outside the calc script at a dp, app, or server level. They simply substitute their textual value at the place they appear in the script. If the substitution results in a valid calc script where it occurs, then you are fine. So FIX ( &subvar ) could be valid.If you mean temporary variables, they hold intermediate calculational values. The docs say "VAR commands can only be assigned values within a member calculation or when VAR is declared. " That is, you may either say 'VAR tempvar = 1000; ' [declare and set value] or 'VAR tempvar;' [declare only, often at the start of your script] then somewhere in the script 'tempvar = expression;' [value gets assigned]. This last expression would not appear within the parentheses of a FIX ( members ) statement, but somewhere within the FIX block. You would never say FIX ( tempvar ) as it is not an outline member.

Problem with FIX-Statement in Business Rule

Hello,
ich have a business rule with two nested FIX-Statements.
I calculate depending on the month in the runtime-prompt a forecast for this month. After that i fix on that month an clear some specific accounts. But some of these accounts still have data.
they are in the cleardata section and they are children of FiBuKonten from the first fix. When i leave out the @CHILDREN("FiBuKonten") in the first fix the accounts are cleared as excepted, but i need that fix because not all accounts are part of this forecast.
I changed everything to work as a calc-script and the same problem appears, on dev and prod database.
Why are some accounts cleared while others not ? Really misterious!
Here is the rule
FIX([TEBIT_RTP_Year],[TEBIT_RTP_Version],"IFRS operativ",[TEBIT_RTP_Entity],"Daten brutto","Daten_brutto_P_M",@CHILDREN("FiBuKonten"))
[TEBIT_RTP_Period](
IF(@ISMBR("Jan"))
Actual_kum = Budget_kum;
ELSEIF(@ISMBR("Feb"))
Actual_kum = Budget_kum;
ELSEIF(@ISMBR("Apr"))
Actual_kum = @ROUND(("1HR"->Dec - Actual_kum->Mar)/9 + Actual_kum->Mar,2);
ELSEIF(@ISMBR("May"))
Actual_kum = @ROUND(("1HR"->Dec - Actual_kum->Apr)/8 + Actual_kum->Apr,2);
ELSEIF(@ISMBR("Jul"))
Actual_kum = @ROUND(("2HR"->Dec - Actual_kum->Jun)/6 + Actual_kum->Jun,2);
ELSEIF(@ISMBR("Aug"))
Actual_kum = @ROUND(("2HR"->Dec - Actual_kum->Jul)/5 + Actual_kum->Jul,2);
ELSEIF(@ISMBR("Oct"))
Actual_kum = @ROUND(("3HR"->Dec - Actual_kum->Sep)/3 + Actual_kum->Sep,2);
ELSEIF(@ISMBR("Nov"))
Actual_kum = @ROUND(("3HR"->Dec - Actual_kum->Oct)/2 + Actual_kum->Oct,2);
ENDIF;)
FIX([TEBIT_RTP_Period])
     CLEARDATA "41000000";
     CLEARDATA "41100000";
     CLEARDATA "41200000";
     CLEARDATA "41990000";
     CLEARDATA "41000900";
     CLEARDATA "41096000";
     CLEARDATA "41196000";
     CLEARDATA "41296000";
     CLEARDATA "41940000";
     CLEARDATA "42000000";
     CLEARDATA "42100000";
     CLEARDATA "42200000";
     CLEARDATA "42099000";
     CLEARDATA "42199000";
     CLEARDATA "42299000";
     CLEARDATA "42990000";
     CLEARDATA "41918000";
     CLEARDATA "41100900";
     CLEARDATA "42091000";
     CLEARDATA "42918000";
     CLEARDATA "54000000";
     CLEARDATA "54009000";
     CLEARDATA "54009900";
     CLEARDATA "54009600";
     CLEARDATA "54130200";
     CLEARDATA "93541175";
     CLEARDATA "54001000";
     CLEARDATA "54001900";
     CLEARDATA "54014000";
     CLEARDATA "54019000";
     CLEARDATA "54021000";
     CLEARDATA "54021900";
ENDFIX
ENDFIX
Thx for your help.
Greets
Kevin

Does it make a difference when a dimension has dynamic calc members and i dont fix on that dimension to fix on the Level 0 members of that dimension ? The result should be the same in my eyes.
SGF is dense. I found out that everytime i the fix includes that first member M_124100 the error occoured.
I changed the rule in the form that i split the FIX Statement. And now it works without the error and with all data cleared. Even when i don`t reorder the dimension SGF.
Again thanks for your help.
Greets
Kevin
FIX([TEBIT_RTP_Year],[TEBIT_RTP_Version],"IFRS operativ",[TEBIT_RTP_Entity],"Daten brutto","Daten_brutto_P_M")
FIX(@CHILDREN("FiBuKonten"))
[TEBIT_RTP_Period](
IF(@ISMBR("Jan"))
Actual_kum = Budget_kum;
ELSEIF(@ISMBR("Feb"))
Actual_kum = Budget_kum;
ELSEIF(@ISMBR("Apr"))
Actual_kum = @ROUND(("1HR"->Dec - Actual_kum->Mar)/9 + Actual_kum->Mar,2);
ELSEIF(@ISMBR("May"))
Actual_kum = @ROUND(("1HR"->Dec - Actual_kum->Apr)/8 + Actual_kum->Apr,2);
ELSEIF(@ISMBR("Jul"))
Actual_kum = @ROUND(("2HR"->Dec - Actual_kum->Jun)/6 + Actual_kum->Jun,2);
ELSEIF(@ISMBR("Aug"))
Actual_kum = @ROUND(("2HR"->Dec - Actual_kum->Jul)/5 + Actual_kum->Jul,2);
ELSEIF(@ISMBR("Oct"))
Actual_kum = @ROUND(("3HR"->Dec - Actual_kum->Sep)/3 + Actual_kum->Sep,2);
ELSEIF(@ISMBR("Nov"))
Actual_kum = @ROUND(("3HR"->Dec - Actual_kum->Oct)/2 + Actual_kum->Oct,2);
ENDIF;)
ENDFIX
FIX([TEBIT_RTP_Period])
CLEARDATA "41000000";
CLEARDATA "41100000";
CLEARDATA "41200000";
CLEARDATA "41990000";
CLEARDATA "41000900";
CLEARDATA "41096000";
CLEARDATA "41196000";
CLEARDATA "41296000";
CLEARDATA "41940000";
CLEARDATA "42000000";
CLEARDATA "42100000";
CLEARDATA "42200000";
CLEARDATA "42099000";
CLEARDATA "42199000";
CLEARDATA "42299000";
CLEARDATA "42990000";
CLEARDATA "41918000";
CLEARDATA "41100900";
CLEARDATA "42091000";
CLEARDATA "42918000";
CLEARDATA "54000000";
CLEARDATA "54009000";
CLEARDATA "54009900";
CLEARDATA "54009600";
CLEARDATA "54130200";
CLEARDATA "93541175";
CLEARDATA "54001000";
CLEARDATA "54001900";
CLEARDATA "54014000";
CLEARDATA "54019000";
CLEARDATA "54021000";
CLEARDATA "54021900";
ENDFIX
ENDFIX

FIX Statement problem

In this calc:
FIX("Actual","Polling",@LEVMBRS ("Measure", 0),"26Apr11":"02Jan12")
DATACOPY "R0003152" TO "R9003152";
ENDFIX
When I try to substitute the ancestors of the date range     from "26Apr11":"02Jan12" to @RELATIVE("P05 FY2012":"P13 FY2012",0), which are equivalent
I am getting an error. Error is : 1200414 Error parsing formula for [FIX STATEMENT] (line 14): number of dimensions [1] does not match number of gen/level [9] in function [@DIM]     .
I can't figure this one out. Anyone see why this is happenng here?

In my Time dimension the hierarchy goes from days ie. 24June11 at level 0 up to Periods (months essentially) P1, P2...
When I copy data from one Org. member to another I need to do it by Period and would prefer to do using Periods, but at the lowest level which is days. I was only looking for a function I could use to identify the lowest level (days) in this dimension by using the Periods members. So, I need to copy data from x member to y member for P2 to P4 for example which would be whatever days that equates to in those periods. I just need a function to bring back the days in those periods for a specified range...like a @LEVMBRS("P2":"P4", 0) but this function does not work in this case.

FIX STATEMENT AND LARGE SPARSE DIMENSIONS

Hello all,
We have the following Essbase BSO db;
Account (Dense) (285 Members) (Aggregating Dimension)
Period (Dense) (65 Members) (Aggregating Dimension)
D1 (Sparse) (3700 Members)
(Aggregating Dimension)
D2 (Sparse) (8900 Members)
(Aggregating Dimension)
D3 (Sparse) (15000 Members)
(Aggregating Dimension)
Version (Sparse) (3 Members) (NON-Aggregating Dimension)
Scenario (Sparse) (5 Members) (NON-Aggregating Dimension)
Year (Sparse) (3 Members) (NON-Aggregating Dimension)
Currency (Sparse) (11 Members) (NON-Aggregating Dimension)
D4 (Sparse) (20 Members) (NON-Aggregating Dimension)
Block Size = ~150KM
Index Cache = 4GB
Data Cache = 8GB
CPUs = 8
MEMORY FREE = 26GB
NOTE:
We are executing the database with data loaded for "JUST" 10 BLOCKS,
SO
VERY VERY SMALL VOLUME OF DATA!!!
We have come across a rather irritating and strange issue while executing
the following calc;
CASE 1: With LEVEL-0 OF RELEVANT
SPARSE DIMENSIONS IN FIX STATEMENT
//ESS_LOCALE English_UnitedStates.Latin1@Binary
SET MSG ERROR;
SET CACHE HIGH;
SET UPDATECALC OFF;
SET LOCKBLOCK HIGH;
SET AGGMISSG OFF;
SET CALCPARALLEL 4;
SET CREATENONMISSINGBLK OFF;
FIX(ACTUAL,"2013",@LEVMBRS(D1,0),@LEVMBRS(D2,0),@LEVMBRS(D3,0),@LEVMBRS(D4,0),
@RELATIVE("EBITDA",0))
DATACOPY ARS->CURRENCY_VERSION TO ARS->WORKING;
DATACOPY CAD->CURRENCY_VERSION TO CAD->WORKING;
DATACOPY CHF->CURRENCY_VERSION TO CHF->WORKING;
DATACOPY COP->CURRENCY_VERSION TO COP->WORKING;
DATACOPY EUR->CURRENCY_VERSION TO EUR->WORKING;
DATACOPY GBP->CURRENCY_VERSION TO GBP->WORKING;
DATACOPY MXN->CURRENCY_VERSION TO MXN->WORKING;
DATACOPY CNY->CURRENCY_VERSION TO CNY->WORKING;
ENDFIX
$$$$$$NOTE1: The above FIX STATEMENT
works just fine and executes in 1 sec as its just a DATACOPY. ESSENTIALLY I
HAVE CREATED THE BLOCKS I WANT TO PERFORM THE BELOW SPARSE CALCULATION$$$$$$
FIX(ACTUAL,"2013",@LEVMBRS(D1,0),@LEVMBRS(D2,0),@LEVMBRS(D3,0),@LEVMBRS(D4,0),
@RELATIVE("EBITDA",0))
ARS = ARS->CURRENCY_VERSION *
"ARS_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CAD = ARS->CURRENCY_VERSION *
"CAD_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CHF = ARS->CURRENCY_VERSION *
"CHF_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
COP = ARS->CURRENCY_VERSION *
"COP_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
EUR = ARS->CURRENCY_VERSION *
"EUR_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
GBP = ARS->CURRENCY_VERSION *
"COP_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
MXN = ARS->CURRENCY_VERSION *
"MXN_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CNY = ARS->CURRENCY_VERSION *
"CNY_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
ENDFIX
$$$$$$NOTE2: The above FIX STATEMENT
is where we have a problem, THE CALC JUST HANGS AND DOES NOT CALCULATE$$$$$$
CASE 2: With “specific” members of
RELEVANT SPARSE DIMENSIONS IN FIX STATEMENT
//ESS_LOCALE English_UnitedStates.Latin1@Binary
SET MSG ERROR;
SET CACHE HIGH;
SET UPDATECALC OFF;
SET LOCKBLOCK HIGH;
SET AGGMISSG OFF;
SET CALCPARALLEL 4;
SET CREATENONMISSINGBLK OFF;
FIX(ACTUAL,"2013",W1,"2251026",MORSCREJWHITE,MORSCREJWHITE_S,KG,TRADESALES)
DATACOPY ARS->CURRENCY_VERSION TO ARS->WORKING;
DATACOPY CAD->CURRENCY_VERSION TO CAD->WORKING;
DATACOPY CHF->CURRENCY_VERSION TO CHF->WORKING;
DATACOPY COP->CURRENCY_VERSION TO COP->WORKING;
DATACOPY EUR->CURRENCY_VERSION TO EUR->WORKING;
DATACOPY GBP->CURRENCY_VERSION TO GBP->WORKING;
DATACOPY MXN->CURRENCY_VERSION TO MXN->WORKING;
DATACOPY CNY->CURRENCY_VERSION TO CNY->WORKING;
ENDFIX
$$$$$$NOTE3: The above FIX STATEMENT
works just fine and executes in 1 sec as its just a DATACOPY. ESSENTIALLY I
HAVE CREATED THE BLOCKS I WANT TO PERFORM THE BELOW SPARSE CALCULATION$$$$$$
FIX(ACTUAL,"2013","2251026",MORSCREJWHITE,MORSCREJWHITE_S,KG,WORKING)
ARS = ARS->CURRENCY_VERSION *
"ARS_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CAD = CAD->CURRENCY_VERSION *
"CAD_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CHF = CHF->CURRENCY_VERSION *
"CHF_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
COP = COP->CURRENCY_VERSION *
"COP_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
EUR = EUR->CURRENCY_VERSION *
"EUR_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
GBP = GBP->CURRENCY_VERSION *
"GBP_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
MXN = MXN->CURRENCY_VERSION * "MXN_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CNY = CNY->CURRENCY_VERSION *
"CNY_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
ENDFIX
$$$$$$NOTE4: The above FIX
STATEMENT works just fine, as I am fixing on just ONE member from relevant
dimensions in the FIX STATEMENT$$$$$$
Please note the only difference between NOTE 2
and NOTE 4 is the FIX statements. I.e., Fixing all required lev-0 members from
required dimensions as opposed to Fixing on just single lev-0 members from
required dimensions.
Also please note that NOTE 1 FIX statement works
just fine! So, there is no problem with the FIX statement itself but rather
with the combination of Sparse Calculations and with Fixing all LEV-0 members
from required dimension in the FIX. Probably because the Sparse dimensions are
VERY LARGE.
Could anyone shed some light on what might be wrong here?
We are on Essbase standalone V11.1.2.
Your inputs are very much appreciated!
Thanks

Hi,
One minor thing I notice - your NOTE 2 problem script does not fix on your Working version, whereas the NOTE 4 script does.
With your small number of blocks, this should not be the problem, but it's probably worth quickly testing and eliminating before delving deeper.
Your script could be invoking member formulae from the Account dimension - does your outline validate ok..?
I cannot tell from your NOTE 4 script which member relates to the Account dimension - is it 2251026?
Whichever it is, it is worth expanding NOTE 4 script up to @RELATIVE("EBITDA",0)....
- if it runs, you know the problem is with your sparse member selections (ie number of blocks being calculated).
- If it doesn't run, then you know there is a problem in calculating one or more of the Accounts under EBITDA. In which case, gradually narrow the range of Accounts to locate the Account or Accounts that trigger the issue. Chances are there's a problem with the member formula

Attributes Issue in FIX Statement Calculation

Hi All,
I have issue with calculating FTE. I have a dimension call Employees and has an attributes (Full-Time / Part-Time). I'm trying to calculate FTE. Below is my code. It seems to be ignoring Attribute in the Fix Statement. when I run this calc script FTE for every employees is 0.5 since that's the last thing it does. If I comment out the second fix statement FTE for every employees is 1. I'm not sure why it's not it's ignoring my statement on the Attributes.
FIX(@LEVMBRS("Time Periods",0),"FY11","WP","Working Version",@LEVMBRS("Measures",0),"USD",@LEVMBRS("Entities",0),@LEVMBRS("Sites",0),@LEVMBRS("Employees",0),@LEVMBRS("Job Codes",0),@LEVMBRS("Cost Centers",0),@LEVMBRS("SBU",0),@LEVMBRS("EE_Status",0),@ATTRIBUTE("Full-Time"))
FTE(
IF
("Base_Salary">0);
"FTE"=1;
ELSE
"FTE"==#MISSING;
ENDIF;
ENDFIX;
FIX(@LEVMBRS("Time Periods",0),"FY11","WP","Working Version",@LEVMBRS("Measures",0),"USD",@LEVMBRS("Entities",0),@LEVMBRS("Sites",0),@LEVMBRS("Employees",0),@LEVMBRS("Job Codes",0),@LEVMBRS("Cost Centers",0),@LEVMBRS("SBU",0),@LEVMBRS("EE_Status",0),@ATTRIBUTE("Part-Time"))
FTE(
IF
("Base_Salary">0);
"FTE"=0.5;
ELSE
"FTE"==#MISSING;
ENDIF;
ENDFIX;
Edited by: user8988798 on Mar 26, 2010 9:57 AM

Having both @LEVMBRS("Employees",0) and @ATTRIBUTE("Full-Time") is your problem. You are saying give me all of the level zero members of employee and also give me the members that have Full time. Since attributes are tied to the base members you would just need @ATTRIBUTE("Full-Time") to get the full time employees

Attributes in FIX statement

When we are using Attributes in the Fix statements of a Business Rule, does it affect the performance? Is it better to use Relative/Children instead of Attributes when it is possible?
Regards,

Does this select ALL of the products, or just the Level 0 products? The reason I ask is that the statement will not be combined using AND logic - only members of different dimensions will be combined using AND logic. Try the following:FIX (@LEVMBRS(Product, 0) AND @ATTRIBUTE(Diet))Now, if your attribute is at level 0 (I assume it is) and you want to select them, just use:FIX (@ATTRIBUTE(Diet))That will select all of the products that have a Diet attribute.Hope that helps.Regards,Jade-------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

How to exclude specified members in a FIX statement used for dataclear?

Hello,
I am not a specialist in writing rules, scripts or formulas.
I want to clear the essbase data base regarding certain entities (for example 0021_LE). This shown Fix statement works.
But what is the best and most effective (performant) way to exclude certain account members (specific accounts) from the flow command CLEARDATA?
/* Fix auf Entities */
FIX ("0021_LE", "0021_DIS")
CLEARDATA "Dec"
/* Ende Fix auf Entities */
Would be glad if somebody would give me any suggestion?
Thanx
AEN

Assuming all the parent level members in the account dimension is dynamic calc.
Tag all the members to be excluded with uda (say excl) and you can write a script as below.
FIX ("0021_LE", "0021_DIS")
FIX(@remove(@levmbrs("Account", 0), @uda("Account", excl)))
CLEARDATA "Dec"
ENDFIX
ENDFIX
If you dont like to tag the uda and assuming "Account1", "Account2", "Account3", "Account4" are to be excluded from the clearing.
you can write a script as below.
FIX ("0021_LE", "0021_DIS")
FIX(@remove(@levmbrs("Account", 0), @list("Account1", "Account2", "Account3", "Account4")))
CLEARDATA "Dec"
ENDFIX
ENDFIX

Essbase Dimension Order in a Fix Statement

Does the dimension order (sparse and dense) make a difference in an Essbase Fix statement? I would appreciate any thoughts. Thanks!

Hi,
I don't think you will ever get a better combination of answers on this subject than at
http://www.network54.com/Forum/58296/thread/1208974485/Order+of+Fixes+-Doesit+matter-
It should answer you question.
Cheers
John
http://john-goodwin.blogspot.com/

Are fix statements in a BR specific to the members selected in the form?

Hi,
I have quite a few business rules. All of my "FIX" statements in the business rules are generic i.e. its fixed based on the attributes. An example is given below
FIX(Inbound,Outbound,@ATTRIBUTE(Transaction_Based),@ATTRIBUTE(Transaction_Based_Queue),@ATTRIBUTE(Transaction_Slab_Based),@ATTRIBUTE(Transaction_Slab_Based_Queue))
My question is, does this fix calculates for all members that have the attribute "Transaction_Based_Queue", does it calculate for all year, all scenarios,all version,all entities,etc.. or it calculates for the members that is selected in the data form?
Regards,
Ragav.

Raghav,
Since you have not FIXED on any particular Year, senario or Version. The script will calculate for all the Years, Scenario and versions. In order to use the values on the webform, do the following steps:
1. Create Global Variables in EAS for Year Scenario and Version.
2. Include the Variable in the FIX Statement FIX([Year], [Scenario], [Version])
3. Attach the Business Rule in the Webform. Change the property of the attached rule to "Pick Value from Dataform" and Hide Prompts.
4. The rule should now pick values from the Data form.
Hope this is helpful.

Multiple Fix Statements

We have calc scripts that are not fixing on one dimension, hence, every member of that dimension is being calc'd. If we have multiple fix statements throughout the calc script, could I just add the missing dimension member to the first fix statement and it would apply throughout the script instead of updating all of the fix statements throughout the script? In essence, once a dimension member is fixed on, it will remain fixed until another fix statement specifially overrides it? I would appreciate any thoughts. Thanks!

Hi Glenn, :)
You are of course and as usual correct re the UNION effect of nested FIX statements that reference the same dimension.
I think the OP was discussing the same member FIXed upon multiple times within the same calc script/HBR. Maybe he has a union occuring and doesn't realize it.
Are you referring to his second post where he states:
Will there be any performance benefits if I change it so that there is one fix statement at the top that's applicable to all calcs, and then change the fix statements subsequently for calcs that need to change their focus?I guess that implies a situation where he first FIXed on Actual and then didn't terminate with an ENDFIX before he went on to FIX on Budget. As you state, that would then cause a union and probably screw his data up in a fairly exciting manner.
Regards,
Cameron Lackpour

[svn:fx-trunk] 11225: Fixed state definition generation.

Revision: 11225
Author:   [email protected]
Date:     2009-10-28 08:20:16 -0700 (Wed, 28 Oct 2009)
Log Message:
Fixed state definition generation.
QE notes: None
Doc notes: None
Bugs: SDK-23655
Reviewer: Paul
Tests run: Checkin, States
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23655
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/StatesModel.java

Dear Pallavi,
Very useful post!
I am looking for similar accelerators for
Software Inventory Accelerator
Hardware Inventory Accelerator
Interfaces Inventory
Customization Assessment Accelerator
Sizing Tool
Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
Request help on such accelerators... Any clues?
Any reply, help is highly appreciated.
Regards
Manish Madhav

@ALIAS in FIX Statement

Similar Messages

Maybe you are looking for