Error in execution of mdx formula in ASO:: Recursion limit[31] reached

Hi,
We are implementing the ASO cube using the Hyperion Essbase version 9.3.1.
Few dimension members need to have formulas which we are writing using the mdx.
Mdx formulas are successfully verified but at retrieval time, it is throwing the following error-
Error executing formula for[604120](line 0) : Recursion limit[31] reached.
In outline, mdx formulas has been assigned to member name '604120' and '604520' in 'Report Line (P/L)' dimension as per business requirement.
Formula on member '604520' = [604120]-[604320] +[604220]
And
Formula on member '604120' =
IIF(
IS([Time].CurrentMember, [Jan]),
([Report Line (P/L)].[604520], [Dec], [Year].CurrentMember.PrevMember),
([Report Line (P/L)].[604520],[Time].CurrentMember.PrevMember, [Year].CurrentMember)
On further investigation, it seems there is dependencies in formulas. And it need to be rewrite.
I am new in mdx queries. Please help me to write. Quick respone will be appreciated.
Thanks & Regards,
Mohit

http://essbase.ru/ wrote:
Check Essbase CFG
- it's Error from settings limitisWhich setting are you referring to for ASO.
Cheers
John
http://john-godowin.blogspot.com/

Similar Messages

Doubt Reg How to implement MDX formula in ASO Cube

We are using Essbase 7x for implementing ASO application, We are struck in implementing MDX formuls in Accounts dimension members. As per the requirement
We have to calculate
Cost Per kilo[Total shipment Cost]/[Billed Weight]
Fuel Surcharge cost per kilo[Fuel Surcharge cost]/[Billed weight]
Need to implement these formula's for the mentioned Accounts members. As we are new to this concept plz let me know if
we wrote these in MDX editor and how to link these to the particulr mrmber in the dimension.please help me out in implementing these formula's

Hi,
1. For ASO cubes also, you can have forumulas on your cube's outline individual members.
2. If the dimension is "accounts" you can write MDX forumulas on the members of the accounts dimension
3. The two members 'cost per kilo' and 'fuel surcharge cost per kilo' and their respective forumulas are Total shipment Cost/Billed Weight and Fuel Surcharge cost/Billed weight.
4. If you have the members like Total shipment Cost,Billed Weight and Fuel Surcharge cost, create 2 account members for which you need to write formulas , then go to 'formula' tab of these members and write a simple division formula.For ASO cubes, no need to end them with semi colon.
One can use MDX editor to write down queries and extract data too, i.e queries . More of it can be found in the DBAG .
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/

ASO Error - Recursion Limit reached

Hi,
I'm getting Recurrsion limit error in ASO while trying to access the data in Excel Addin. I set CALCLIMITFORMULARECURSION FALSE in essbase.cfg but still facing the same error. Any help would be appreciated...
Essbase Version 11.1.13
"Error executing formula for [MemeberName] (line 0): Recursion Limit [31] Reached"
Thanks
Edited by: MoFa on Jul 26, 2012 4:48 PM

Hi,
CALCLIMITFORMULARECURSION configuration setting is not valid for ASO cubes and only applies to BSO cubes. The equivalent configuration setting for ASO cubes is MDXLIMITFORMULARECURSION.
Syntax
MDXLIMITFORMULARECURSION TRUE | FALSE
TRUE - Imposes a limit of 31 on the number of MDX formula execution levels. The default setting is TRUE.
FALSE - Imposes no limit on the number of MDX formula execution levels.
Description
MDXLIMITFORMULARECURSION limits the number of execution levels of MDX calculated members or formulas. MDX calculated member or formula execution may be recursive (for example, a formula can refer to itself, or a calculated member can refer to itself). By default, Essbase limits the number of MDX formula execution levels, because formulas with excessive execution levels may lead to stack overflow errors and crash the server. However, setting MDXLIMITFORMULARECURSION to FALSE prevents Essbase from imposing the limitation. You can use this setting when you know that a recursive execution in a formula/calculated member will eventually terminate, and you wish to have a recursion depth greater than 31.
If an MDX formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is not set, or is set to TRUE, Essbase stops processing that formula and writes
error messages in the application log. If a formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is set to FALSE, Essbase continues processing that formula.
CAUTION: before setting MDXLIMITFORMULARECURSION to FALSE, be sure that the MDX formulas in the outline are not infinitely recursive; for example, be sure that formulas do not depend on each other. Infinite formula recursion may crash the server.
This is a known issue and is fixed in version 11.1.1.3.500 and you may consider upgrading Essbase.
KosuruS

Essbase 11.1.2.1 - Converting BSO Member Formula to ASO MDX Formula

Hi all,
I'm quite new at Essbase and I'm currently using Essbase 11.1.2.1. I have 2 cubes: one is a BSO cube and the other is an ASO cube.
In the BSO cube, I have an account that has member formula:
IF(@ISATTRIBUTE("US"))
("Sales"->"Budget"->"USD")-("Sales"->"Actual"->"USD");
ELSEIF(@ISATTRIBUTE("EU"))
("Sales"->"Budget"->"EUR")-("Sales"->"Actual"->"EUR");
ELSEIF(@ISATTRIBUTE("UK"))
("Sales"->"Budget"->"GBP")-("Sales"->"Actual"->"GBP");
ENDIF
Notes:
- Sales is an account
- US, EU, and UK are members of Country attribute dimension
- Budget and Actual are members of Scenario dimension
- USD, EUR, and GBP are members of Currency dimension
I understand that the member formula for BSO and ASO are different. Can anyone please advise me on what the formula should be in ASO cube as MDX formula?
Thank you very much!

CASE [Currency].CurrentMember.[Country]
     WHEN "US" THEN ([Sales], [Budget], [USD]) - ([Sales], [Actual], [USD])
     WHEN "EU" THEN ([Sales], [Budget], [EUR]) - ([Sales], [Actual], [EUR])
     WHEN "UK" THEN ([Sales], [Budget], [GBP]) - ([Sales], [Actual], [GBP])
     ELSE 0
END
*Note that I am assuming Country is an attribute of Currency based on the information provided.

Bso formula to aso

BSo formula
IF(@ISMBR(@IDESCENDANTS ("Health Companies")))
"H42000.Calc" = (("H40900"->"NG_Opt"+"H41000"->"NG_Opt"
+"H41100"->"NG_Opt"+"H41200"->"NG_Opt"+"H41300"->"NG_Opt"
+"H41400"->"NG_Opt"+"H41700"->"NG_Opt")*
("NG_11Adj"->"PLAT_00"->"BSEG_00"->"HMHS_00000"->"PROD_000"->"MKT_0000"->"DEPT_00000"->"FAC_00000"->"LAE Rate"));
ASO formula
CASE when is (Company.CurrentMember, [Health companies]) Then
[H42000.calc] = (([H40900],NG_opt + [H41000],NG_opt + [H41100],NG_opt + [H41200],NG_opt + [H41300],NG_opt
+[H41400],NG_opt + [41700],NG_opt)*
(NG_Adj.currentmember, Plat_00.currentmember, BSEG_00.currentmember,HMHS_00000.currentmember,
PROD_000.currentmember, MKT_0000.currentmember,DEPT_00000.currentmember,FAC_00000.currentmember,
LAERate )
End
i am trying to convert bso formula into aso .
i am getting error message
Error(1260052) syntax error in input mdx query on line 2 at token '=' NG_21Adj
i am writing member formula for NG_21Adj and it looks like it is not taking '=' and '+' sign
can anyone help me with this
thank you

Oh (of course). In ASO member formula the calc is for that member, so the equation is not necessary.
But I'm confused because you said this member formula was on a member called NG_21Adj
So where does H42000.calc come from?
Below should work syntactically, but now I am not clear what your objective is. Which member are you trying to calculate?
CASE WHEN IsAncestor([Health Companies], [Company].CurrentMember, INCLUDEMEMBER) THEN
(([H40900], [NG_opt]) + ([H41000], [NG_opt]) + ([H41100], [NG_opt]) + ([H41200], [NG_opt]) + ([H41300], [NG_opt]) + ([H41400], [NG_opt]) + ([41700], [NG_opt])) *
([NG_Adj], [Plat_00], [BSEG_00], [HMHS_00000], [PROD_000], [MKT_0000], [DEPT_00000], [FAC_00000], [LAERate]) ENDor
CASE WHEN IsAncestor([Health Companies], [Company].CurrentMember, INCLUDEMEMBER) THEN
SUM(CROSSJOIN({[H40900], [H41000], [H41100], [H41200], [H41300], [H41400], [41700]}, {[NG_opt]})) * ([NG_Adj], [Plat_00], [BSEG_00], [HMHS_00000], [PROD_000], [MKT_0000], [DEPT_00000], [FAC_00000], [LAERate]) END

Need help with MDX formula to sum months

I was able to use Gary C's suggestion to sum daily data for 90 days with the following formula.
SUM( TAIL( TUPLERANGE(
([FY_2006], [01/01]), ([Scenario].CurrentMember,
[Time].CurrentMember) ), 90 ))
This formula works great - even when crossing different years in the Scenario dimension.
I'm now trying to sum the prior 3 months using a similar TupleRange command:
SUM( TAIL( TUPLERANGE(
([FY_2006], [JAN]), ([Scenario].CurrentMember,
[Time].CurrentMember) ), 3 ))
I'm running into an issue due to additional parents in the time dimension. January and February of the current year are pulling data from the children of another parent in the Time dimension as opposed to Nov and Dec from prior year.
My Time dimension is setup as follows:
Time
|
|-Total Year
| |-Jan
| | |-01/01
| | |-01/02...
| |.
| |-Feb... Dec (each month has days as children)
|.
|.
|-QTDs
| |- Various parents and shared children
|.
|-Weeks
| |-FY08_Weeks
| |.
| |-FY09_Weeks
Using the previous TupleRange command, when I retrieve data for Jan it retrieves data from the following members:
Jan
FY08_Weeks
FY09_Weeks
Any suggestions on how I can write the MDX formula so my 3 Month formula pulls in the correct members? (That is, it should only pull in members from the 'Total Year' parent.)

In ASO architecture, if you want to aggregate these multiplied values you probably want to do the multiplication prior to loading so the sum of the products rolls up. Right now, you can't have the multiplication done in MDX and then have ASO aggregate. It's mostly a performance concern; you can do the multiplication and aggregation in one formula if you want. The basic multiplication is just [Standard Material Per Unit] * [Units Sold] To aggregate, you need to wrap in additional clauses. I've attached code here so you can see it with indenting- I believe that consistent indenting helps catch a lot of syntax errors. You will also need to assign the formula to a new member (account or otherwise). If you only want to see the values at level-0 and you don't want them aggregated, it's very easy: iif ( [Product].CurrentMember.[LEVEL_NUM] = 0, [Standard Material Per Unit] * [Units Sold], MISSING )

Inconsistent results with MDX formula

Hi. I'm converting a BSO cube to ASO, and it has dynamically calculated formulas that I'm converting to MDX. I have a formula that is supposed to accumulate an account (Order Intake) through the months and years until it gets to the current month of the current year (set by substitution variables) and then just carries that balance forward until the end.
This is the formula I wrote in MDX.
IIF( Count( Intersect( {MemberRange([Years].[FY95], [&Auto_CurYr].Lag(1))}, {Years.CurrentMember} ) ) = 1,
IIF(CurrentMember ([Period]) = [Jan],
[Order Intake] + ([Contract Value],[Adj],[Years].CurrentMember.PrevMember),
[Order Intake] + ([Contract Value],[Period].CurrentMember.PrevMember)
IIF( CurrentMember ([Years]) = [&Auto_CurYr],
IIF( CurrentMember ([Period]) = [Jan],
[Order Intake] + ([Contract Value],[Adj],[Years].CurrentMember.PrevMember),
IIF( Count( Intersect( {MemberRange([Period].[Feb], [&Auto_CurMoNext_01].Lag(1))}, {Period.CurrentMember} ) ) = 1,
[Order Intake] + ([Contract Value],[Period].CurrentMember.PrevMember),
([Contract Value],[Period].CurrentMember.PrevMember)
([Contract Value],[Adj],[Years].CurrentMember.PrevMember) /*This is the statement that evaluates for months and years after the current month and year*/
The inconsistent results are as follows:
I have a spreadsheet that has the years and months across the top in columns. The substitution variables are set to FY09 for the year and Oct for the month. The formula works fine until it gets to Jan of FY10, at which point it produces a number out of thin air, and carries that incorrect number through to the end.
When I put the years and months into my rows, however, and then drill down on the months, I get different results. Not only different, but different results at different times, too. When I first drilled, all results were correct. Now when I drill, it produces a random number in October of FY09 (not entirely random, but actually double what it's supposed to be), then #missing in Nov of FY09, then the correct number thereafter. Same exact data intersection on both spreadsheets, different results. I've retrieved over and over again, and the only time it might change is if I re-drill. I've used both Essbase Add-in and Smart View with consistently inconsistent results.
Has anyone ever encountered this sort of behavior with an MDX formula?

Well, I finally got a formula that works. I did end up using a combination of CASE and IIF, but I never did figure out how to deal with summing up ranges of data correctly, accounting for changing substitution variables, so I had to do a lot of hard coding by month. For instance, I couldn't ask it to sum([Order Intake],[Jan],[&Auto_CurYr]:([Order Intake],[&Auto_CurMo],[&Auto_CurYr]). Although it validated fine, when I tried to retrieve it said members were not of the same generation, presumably because my substitution variable could potentially be a non - level 0 month (it worked if I hard coded the end month). Also, I really don't like the MDX version of @LSIBLINGS and @RSIBLINGS.
But this works.
CASE
When Count( Intersect( {MemberRange([Years].[FY95], [&Auto_CurYr].Lag(1))}, {Years.CurrentMember} ) ) = 1
THEN IIF(CurrentMember ([Period]) = [Jan],
[Order Intake] + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Feb],
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Feb]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Mar],
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Mar]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Apr],
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Apr]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [May],
Sum(CrossJoin({[Order Intake]}, {[Jan]:[May]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Jun],
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Jun]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Jul],
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Jul]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Aug],
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Aug]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Sep],
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Sep]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Oct],
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Oct]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Nov],
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Nov]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Dec]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember))
When CurrentMember ([Years]) IS [&Auto_CurYr]
THEN IIF(CurrentMember ([Period]) = [Jan],
[Order Intake] + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Feb] AND CONTAINS([Feb], {MEMBERRANGE([&Auto_CurMoNext_01].FirstSibling, [&Auto_CurMoNext_01].Lag(1))}),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Feb]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Mar] AND CONTAINS([Mar], {MEMBERRANGE([&Auto_CurMoNext_01].FirstSibling, [&Auto_CurMoNext_01].Lag(1))}),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Mar]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Apr] AND CONTAINS([Apr], {MEMBERRANGE([&Auto_CurMoNext_01].FirstSibling, [&Auto_CurMoNext_01].Lag(1))}),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Apr]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [May] AND CONTAINS([May], {MEMBERRANGE([&Auto_CurMoNext_01].FirstSibling, [&Auto_CurMoNext_01].Lag(1))}),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[May]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Jun] AND CONTAINS([Jun], {MEMBERRANGE([&Auto_CurMoNext_01].FirstSibling, [&Auto_CurMoNext_01].Lag(1))}),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Jun]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Jul] AND CONTAINS([Jul], {MEMBERRANGE([&Auto_CurMoNext_01].FirstSibling, [&Auto_CurMoNext_01].Lag(1))}),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Jul]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Aug] AND CONTAINS([Aug], {MEMBERRANGE([&Auto_CurMoNext_01].FirstSibling, [&Auto_CurMoNext_01].Lag(1))}),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Aug]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Sep] AND CONTAINS([Sep], {MEMBERRANGE([&Auto_CurMoNext_01].FirstSibling, [&Auto_CurMoNext_01].Lag(1))}),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Sep]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Oct] AND CONTAINS([Oct], {MEMBERRANGE([&Auto_CurMoNext_01].FirstSibling, [&Auto_CurMoNext_01].Lag(1))}),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Oct]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
IIF(CurrentMember ([Period]) = [Nov] AND CONTAINS([Nov], {MEMBERRANGE([&Auto_CurMoNext_01].FirstSibling, [&Auto_CurMoNext_01].Lag(1))}),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[Nov]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember)),
Sum(CrossJoin({[Order Intake]}, {[Jan]:[&Auto_CurMo]})) + sum(([Order Intake],[YearTotal],[FY95]):([Order Intake],[YearTotal],[Years].CurrentMember.PrevMember))
WHEN CONTAINS([Years].CurrentMember, {MemberRange([&Auto_CurYr].Lead(1), [Years].[FY15])})
THEN ([Contract Value],[Adj],[Years].&Auto_CurYr)
END
Thanks for looking at it, Gary, I appreciate it.
Sabrina
Edited by: SabrinaD on Nov 18, 2009 2:29 PM
Edited by: SabrinaD on Nov 18, 2009 2:31 PM
Edited by: SabrinaD on Nov 18, 2009 2:34 PM
Edited by: SabrinaD on Nov 18, 2009 2:35 PM

VARIABLE IN MDX FORMULA

Hello,
I have a package which only rund a logic,
this package enables to select an entity on which the logic will run
so in my package assign parameters component , i have my prompt
PROMPT(SELECTINPUT,%MY_ENTITY%,"Enter the entity",,"%ENTITY_DIM%")
and then
TASK(Execute formulas,USER,%USER%)
TASK(Execute formulas,APPSET,%APPSET%)
TASK(Execute formulas,APP,%APP%)
TASK(Execute formulas,SELECTION,%SELECTIONFILE%)
TASK(Execute formulas,FORMULASCRIPT,"*FUNCTION MYENTIY=%MY_ENTITY%")
TASK(EXECUTE FORMULAS,LOGICFILE,TEST.LGF)
in my logic, i want to use the entity put in the package in a mdx formula,
*MEMBERSET(%Ent_R%,"DESCENDANTS(FILTER([ENTITE].MEMBERS,[ENTITE].CURRENTMEMBER.PROPERTIES("ENTITE_REF")=MYENTITY),99,LEAVES)")
the variable MYENTITY isn't working, so my variable %Ent_R% is corrupted too
how can i change the syntax in order to include MYENTITY parameter please
i have tried so many things, i'm stuck
thanks in advance
regards
CL

Hello,
First of all, most sincere thanks for replying, i'm stuck and blocked and beginner in logic and have no collegue around me to advice me or help me, and i've tried so many things that i end up mixing them
the problem is that the follwing syntax
*MEMBERSET(%Ent_R%,"DESCENDANTS(FILTER([ENTITE].MEMBERS,[ENTITE].CURRENTMEMBER.PROPERTIES("ENTITE_REF")=%ENTITY_SET%),99,LEAVES)")
isn't validated when i do a "validate and process logic" it rejects me by giving this message
error in step 1 of QueryCubeAndDebug:-2147217900 Formula error - syntax error - token is not valid: "{DESCENDANTS(FILTER([ENTITE].MEMBERS,[ENTITE].CURRENTMEMBER.PROPERTIES("ENTITE_REF")=^%^ENTITY_SET%),99,LEAVES)}"
when i put the variable name around commas like ' ' or " "
this way for instance
*MEMBERSET(%Ent_R%,"DESCENDANTS(FILTER([ENTITE].MEMBERS,[ENTITE].CURRENTMEMBER.PROPERTIES("ENTITE_REF")="%ENTITY_SET%"),99,LEAVES)")
the logic validates, the package runs but no data are written
in the debuglogicfile, it seems that it doens't recongnize the fact that it is a variable, and put it as string
i really don't know how to put it

MDX Formulas

Are MDX formulas used only in ASO cubes or we can use it BSO as well.
I looked into the Essbase DBAG, But could not find the right information. If anybody know about this, please clarify.
Thanks for the Help in advance..........

Hi ,
One can use MDX script editor to retrive data from BSO cubes .
But, As far as the member formulas of the ASO outline is concerned , we got to use the MDX only.
I have tried this on the 7X version.
Sandeep Reddy Enti
HCC
http://analytiks.blogspot.com

ORA-04088: error during execution of trigger

Error Description :
We have more than 100 of records in a csv file which we are processing through a script. At the first execution let
say it generates trigger exception for five records ... when I execute the script second time those five records
are not throwing any exception but may be some other records. But consecutive trigger exception is not happening for any record . If a particular record is throwing exception at first attempt then in the second attempts it's not throwing the trigger exception.
Input file
PROPRTY_ID,NAME,OLD STREET,CITY,STATE,ZIP,NEW STREET,NEW CITY,NEW STATE,NEW ZIP
88527091,SAM PAUL SUMMU ,1061 XYZ,CITY1,ST,95626,5512 XX YY ZZ,TOWN,PA,12345-9812
Error :
88527091,SAM PAUL SUMMU ,1061 XYZ,CITY1,ST,95626,5512 XX YY ZZ,TOWN,PA,12345-9812 - PROPERTY Update Error : ORA-00001: unique constraint (PROD.PK_AUDIT_LOG) violated
ORA-06512: at "PROD.PROPERTY_AUD", line 159
ORA-04088: error during execution of trigger 'PROD.PROPERTY_AUD'
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> desc property
Name Null? Type
PROPERTY_ID NOT NULL NUMBER(20)
TYPE_CODE VARCHAR2(10)
TYPE_PREFIX VARCHAR2(10)
DWELLING_TYPE_CODE NOT NULL VARCHAR2(10)
DWELLING_TYPE_PREFIX NOT NULL VARCHAR2(10)
STREET_NUMBER VARCHAR2(25)
STREET_DIRECTION CHAR(2)
STREET_NAME NOT NULL VARCHAR2(45)
UNIT_NUMBER VARCHAR2(15)
CITY_CODE VARCHAR2(10)
STATE NOT NULL CHAR(2)
ZIP_CODE VARCHAR2(10)
UNIT_TYPE VARCHAR2(10)
UNIT_PREFIX VARCHAR2(10)
COUNTY_CODE VARCHAR2(10)
COUNTRY_CODE NOT NULL VARCHAR2(10)
SQUARE_FEET NUMBER(6)
NUMBER_MOTHER_LAW_UNITS NUMBER(6)
YEAR_BUILT DATE
PROPERTY_VALUE NUMBER(12)
ZIP_PLUS_4 VARCHAR2(4)
SFI_REQ_FLAG CHAR(1)
LAST_MODIFIED NOT NULL DATE
LAST_MODIFIED_BY VARCHAR2(31)
STANDARDIZED_STATUS VARCHAR2(10)
STANDARDIZED_DESC VARCHAR2(200)
SQL> desc audit_log
Name Null? Type
SEQ_NO NOT NULL NUMBER(20)
TABLE_NAME VARCHAR2(31)
USER_STAMP VARCHAR2(31)
TIME_STAMP DATE
TRAN_CODE CHAR(2)
RECORD1 VARCHAR2(2000)
RECORD2 VARCHAR2(2000)
FLAG_FLD CHAR(1)
SFI_FLAG_FLD CHAR(1)
ERROR_NUMBER NUMBER
Update Query which is getting executed :
UPDATE PROPERTY
SET DWELLING_TYPE_CODE = 'SFR',
DWELLING_TYPE_PREFIX = 'DWELLING',
STREET_NUMBER = NULL,
STREET_DIRECTION = NULL,
STREET_NAME = ln_new_street_name, -- <From input file>
UNIT_NUMBER = NULL,
CITY_CODE = ln_city_code, -- <From other Table>
STATE = ln_new_state, -- <From input file>
ZIP_CODE = ln_new_zip_code,
UNIT_TYPE = NULL,
UNIT_PREFIX = NULL,
COUNTY_CODE = ln_county_code, -- <From Other table>
COUNTRY_CODE = 1,
ZIP_PLUS_4 = ln_zip_plus_4 -- <From Input file>
WHERE PROPERTY_ID = ln_property_id; -- <From Other table>
*NOTE :* Property.LAST_MODIFIED field is auto populate through other trigger. It does not causing any problem.
This might be helpful :
SQL> select OWNER, CONSTRAINT_NAME, TABLE_NAME,COLUMN_NAME from dba_cons_columns where CONSTRAINT_NAME='PK_AUDIT_LOG';
OWNER CONSTRAINT_NAME TABLE_NAME COLUMN_NAME
PROD PK_AUDIT_LOG AUDIT_LOG SEQ_NO
PROD_ARCH PK_AUDIT_LOG AUDIT_LOG SEQ_NO
SQL> select SEQ_NO, trim(RECORD1), trim(RECORD2),TIME_STAMP
from audit_log where RECORD1 like '%BUTTE%' order by TIME_STAMP;
SEQ_NO
1675677212
TRIM(RECORD1)
00000000000031814095...SFR .DWELLING ...5512 BUTTE VIEW CT ..15532
 .CA.95765 ...1377 .1 .....5000..20100922.SUSMSAHA ..
TRIM(RECORD2)
00000000000031814095...SFR .DWELLING ...5512 BUTTE VIEW CT ..15532
 .CA.95765 ...1377 .1 .....5000..20100922.SUSMSAHA ..
TIME_STAMP
22-sep-2010
Trigger Body which is fired and throwing the exception :
create or replace trigger PROPERTY_AUD
before insert or update on PROPERTY
for each row
declare
rec1 varchar2(2000);
rec2 varchar2(2000);
tcode char(1);
ln_seq_id NUMBER:=Null;
ls_sql VARCHAR2(2000):=Null;
begin
select temp_audit_seq.nextval into ln_seq_id from dual;
rec1 := null;
rec2 := null;
 if user = 'NONREP_USER' then
 return;
 end if;
 if (dbms_reputil.from_remote = FALSE) then
 :NEW.last_modified := sysdate;
 if (user = 'SALESFORCE_SYNC') then
 :new.last_modified_by := NVL(:new.last_modified_by,USER);
 else
 :new.last_modified_by := user;
 end if;
 end if;
if inserting then
rec1 :=
LPAD(:new.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:new.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:new.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:new.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:new.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:new.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.STATE, 2, ' ' ) || '.' ||
RPAD(:new.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:new.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:new.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:new.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:new.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:new.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:new.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_DESC, 200, ' ' );
tcode := 'I';
elsif deleting then
rec1 :=
LPAD(:new.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:new.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:new.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:new.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:new.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:new.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.STATE, 2, ' ' ) || '.' ||
RPAD(:new.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:new.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:new.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:new.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:new.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:new.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:new.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_DESC, 200, ' ' );
tcode := 'D';
else
rec1 :=
LPAD(:old.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:old.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:old.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:old.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:old.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:old.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:old.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:old.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:old.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:old.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:old.STATE, 2, ' ' ) || '.' ||
RPAD(:old.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:old.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:old.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:old.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:old.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:old.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:old.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:old.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:old.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:old.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:old.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:old.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:old.STANDARDIZED_DESC, 200, ' ' );
rec2 :=
LPAD(:new.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:new.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:new.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:new.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:new.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:new.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.STATE, 2, ' ' ) || '.' ||
RPAD(:new.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:new.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:new.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:new.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:new.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:new.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:new.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_DESC, 200, ' ' );
tcode := 'U';
end if;
ls_sql :='
INSERT INTO AUDIT_LOG
( seq_no,
table_name,
user_stamp,
time_stamp,
tran_code,
record1,
record2)
VALUES
( :id,
:s_table_name,
:s_user_name,
:d_sysdate,
:s_tcode,
:s_rec1,
:s_rec2
EXECUTE IMMEDIATE ls_sql
USING ln_seq_id,
'PROPERTY',
user,
sysdate,
tcode,
rec1,
rec2;
end;
Your suggestion is highly appreciated ..
Edited by: Bipul on Sep 23, 2010 12:40 AM

TEMP_AUDIT_SEQ generates number with the increment of +1
Although there seems other sequence populating the AUDIT_LOG table through a different sequence with the increment of +10. So till now there are already 1179 different numbers residing in audit_log.seq_no and yet to be generated by the TEMP_AUDIT_SEQ sequence. I will look into more details.
SQL> select max(seq_no) from audit_log;
MAX(SEQ_NO)
1675689121
SQL> select TEMP_AUDIT_SEQ.nextval from dual;
 NEXTVAL
1675677285
SQL> select count(*) From audit_log where seq_no>1675677285;
COUNT(*)
 1179
SQL> select count(*) from audit_log where seq_no>1675677283 and mod(seq_no,2)=1;
COUNT(*)
 1179
SQL> select seq_no from audit_log where seq_no>1675677283 and mod(seq_no,2)=1 and rownum<12;
 SEQ_NO
1675677291
1675677301
1675677311
1675677321
1675677331
1675677341
1675677351
1675677361
1675677371
1675677381
1675677391
11 rows selected.
Thank you Lee and Herald ten Dam ...

Problem in taking correct Substitution variable in MDX Formula

Hi,
We have MDX Formula which takes Substitution Variable as input . Previously we used Hyperion Essbase 9.3.1.3 version and working fine currently we upgraded to 11.1.1.3 version After Upgrade this formula is not taking correct updated value. Its taking previously updated value . To Take the Correct value we are bouncing the Essbase Services then only new Formula is picking the latest Updated value. This is happening only for one formula and rest everything is working fine. Can you please tell us is there any bug or where is the problem is ?
Thanks,
Naresh.

The Database Administrator's Guide and the Essbase Technical Reference are available through the documentation portal:
http://download.oracle.com/docs/cd/E17236_01/nav/portal_3.htm
Both the Database Administrator's Guide and the Technical Reference are searchable on an exact phrase, to find the source of the extract John provided.
http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/dotcreat.html#dotcreat1053369
See section "Setting Substition Variables".

On closing Acrobat Windows detect an error "Data Execution Prevention has closed Adobe Acrobat".

Hi,
I developed a plugin which captures Before/After open, close and save events and perform some operation inside these events.
I tested the plugin in Windows XP and Acrobat 9.0.0 and 10.0.0 and everything works fine. But when in test my plugin on Windows Server 2008 Standard 32 bits, then windows detect an error while closing the acrobat and shows the following message:
"Data Execution Prevention has closed Adobe Acrobat"
I am using Acrobat 10.0.0 for testing in Windows Server 2008 operating system. Also, debugging the program shows no error but plugin does not produce the desired result when tested on Windows Server 2008 Standard 32 bits operating system.
Can anyone please giude me how to resolve this issue??
Thanks in advance!

Are you really using 10.0.0? You've installed no updates to it??
From: poortip87 <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Date: Mon, 6 Feb 2012 21:46:02 -0800
To: Leonard Rosenthol <[email protected]<mailto:[email protected]>>
Subject: On closing Acrobat Windows detect an error "Data Execution Prevention has closed Adobe Acrobat".
On closing Acrobat Windows detect an error "Data Execution Prevention has closed Adobe Acrobat".
created by poortip87<http://forums.adobe.com/people/poortip87> in Acrobat SDK - View the full discussion<http://forums.adobe.com/message/4190399#4190399

Error in execution in RSA3

Hi Experts,
When executing a FM based extractor i got error 'Error in execution'. The log says 'Update mode not supported by API'.
I checked in debugging mode the update mode not getting reflected from standard program whtever mode in RSA3.
Please suggest any pointers or oss notes on this.
Thanks
Konda Reddy

hi konda.
plzz go through these threads.
Update mode F not supported by the extraction api
update mode R is not supported by extraction API
https://forums.sdn.sap.com/click.jspa?searchID=22615890&messageID=6822401
Update mode R is not supported by the extraction API
hope this will help u

Error in a while loop formula

I am trying to use a while loop formula to show the characters in a field up to the open parentheses '(', however I am recieving an error message saying: 'A subscript must be between 1 and the length of the string.'_
There are values in the field that will not have any perentheses at all, such as 'N/A' and I think this may be what is returning the error?? My original formula is:
local NumberVar i:=1;
Local StringVar Severity;
while {Issue_Lookups_1.Name}<> '(' do
(if {Issue_Lookups_1.Name}<> '(' then Severity:= Severity + {Issue_Lookups_1.Name};
i:= i+1);
Severity
I also tried this variation, creating a secong formula to exclude any values = to N/A
First formula:
if {Issue_Lookups_1.Name}<> "N/A" then {Issue_Lookups_1.Name} else ''
While Loop formula:
local NumberVar i:=1;
Local StringVar Severity;
while {@Severity<>N/A}<> '(' do
(if {@Severity<>N/A}<> '(' then Severity:= Severity + {@Severity<>N/A};
i:= i+1);
Severity

Try this
local NumberVar i:=1;
Local StringVar Severity;
while not({@SeverityN/A} = '(') do
(if not({Issue_Lookups_1.Name} ='(' ) then Severity:= Severity + {Issue_Lookups_1.Name};
i:= i+1);
Severity
Regards,
Raghavendra
Edited by: Raghavendra Gadhamsetty on Feb 11, 2009 6:56 PM

Problem in writing outline formula in ASO

Hi All,
I am encountering a problem in my ASO cube where in Ending_VendorBalance is the parent of Beg_VendorBalance, VendorBalance_Acquisition and Netflow. We get values for VendorBalance_Acquisition and Netflow through 0 level data but not for Beg_Vendor Balance. Beg_VendorBalance is calculated as the value of last month of Ending_VendorBalance. How can we achieve this using outline formula in ASO?
Ending_VendorBalance <3>
Beg_VendorBalance [0: Case when(is(month.currentmember,Sep)) and then 0 else]
VendorBalance_Acquisition (Alias: Vendor balance at acquisition (will not change)) (UDAS: TB_Last)
NetFlow <3>
Pls suggest.
Regards,
Karan

One way I can think of is to logically group members under parents in the outline, that way you can simply use the parent name.children.
Robert

Error in execution of mdx formula in ASO:: Recursion limit[31] reached

Similar Messages

Maybe you are looking for