Essbase Cube - QTD

Hi there,
Data loaded in my cube is at QTD level on daily basis. I need to be able to keep QTD data that was loaded in previous weeks of the quarter and be able to WTW analysis on any given day by looking up any week previously. Can someone please advise what is the best way of doing this.
Regards,
B

I'll assume yout qtd member is where the data is loaded and in a ddifferent dimension than your time dimension and yout time time dimension is called Periods. you could create a member called daily and use something like (note I hanve not tested this as I'm just typing it here)
Case when islevel(periods.currentlevel(0)) Then
(QTD.currentmember ,Periods.currentmember) - (QTD.currentmember ,Periods.currentmember.lag(1))
ELSE
SUM(QTD,Periods.currentmember.children)
END
I'm sure Gary Crisi can give you the actual syntax
Note, the QTD and Period names should have square brackets around them but the editor thinks they are html tags and trats them oddly
Edited by: GlennS_2 on Dec 22, 2008 6:49 PM

Similar Messages

  • Essbase Studio: Failed to deploy Essbase cube

    Hi
    I have started working with Essbase studio sometime back and I am able to deploy BSO cube with success using the TBCSample Database which comes along with Essbase. Now I wanted to deploy ASO cube, as no sample database is available I thought to create one, I extracted ASOSamp using ODI to CSV files. Then I bulk inserted the csv extracts into MSSQL 2003 server which created 11 tables (Age, Geography, IncomeLevel, Measures, PaymentType, Product, Stores, Time TransactionType, Year). The above mentioned table does not have any keys(Primary, Foreign) as it is an Essbase export.
    I then successful created ASO Cube Schema using the newly created sample database in MSSQL, validated cube schema without any errors.
    Essbase Property Setting:
    Measures Hierarchy is tagged as Dynamic Compression at dimension level
    Time, Product and Year Hierarchy is tagged as Multiple Hierarchies Enabled, Year does not have multiple hierarchies but it has formulas for Variance and Variance % member. Is there a way to tag Year as Dynamic hierarchy?
    But when I try to deploy the cube to Essbase I receive following errors:
    Failed to deploy Essbase cube
    Caused By: Cannot end incremental build. Essbase Error(1060053): Outline has errors
    \\Record #1 - Member name (Time) already used
    + S Time + S
    \\Record #6 - Member name (1st Half) already used
    MTD + S 1st Half + S
    \\Record #7 - Member name (2nd Half) already used
    MTD + S 2nd Half + S
    \\Record #21 - Member name (Qtr1) already used
    Qtr1 + S Feb + S
    \\Record #22 - Member name (Qtr1) already used
    Qtr1 + S Jan + S
    \\Record #23 - Member name (Qtr1) already used
    Qtr1 + S Mar + S
    \\Record #24 - Member name (Qtr2) already used
    Qtr2 + S Apr + S
    \\Record #25 - Member name (Qtr2) already used
    Qtr2 + S Jun + S
    \\Record #26 - Member name (Qtr2) already used
    Qtr2 + S May + S
    \\Record #27 - Member name (Qtr3) already used
    Qtr3 + S Aug + S
    \\Record #28 - Member name (Qtr3) already used
    Qtr3 + S Jul + S
    \\Record #29 - Member name (Qtr3) already used
    Qtr3 + S Sep + S
    \\Record #30 - Member name (Qtr4) already used
    Qtr4 + S Dec + S
    \\Record #31 - Member name (Qtr4) already used
    Qtr4 + S Nov + S
    \\Record #32 - Member name (Qtr4) already used
    Qtr4 + S Oct + S
    \\Record #33 - Member name (Time) already used
    Time + S MTD + S
    \\Record #34 - Member name (Time) already used
    Time ~ S QTD ~ S
    \\Record #35 - Member name (Time) already used
    Time ~ S YTD ~ S
    \\Record #9 - Error adding Attribute to member QTD(Jan) (3320)
    \\Record #9 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD + S QTD(Jan) + S [Jan]
    \\Record #10 - Error adding Attribute to member QTD(Apr) (3320)
    \\Record #10 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Apr) ~ S [Apr]
    \\Record #11 - Error adding Attribute to member QTD(Aug) (3320)
    \\Record #11 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Aug) ~ S [Jul]+[Aug]
    \\Record #12 - Error adding Attribute to member QTD(Dec) (3320)
    \\Record #12 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Dec) ~ S [Oct]+[Nov]+[Dec]
    \\Record #13 - Error adding Attribute to member QTD(Feb) (3320)
    \\Record #13 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Feb) ~ S [Jan]+[Feb]
    \\Record #14 - Error adding Attribute to member QTD(Jul) (3320)
    \\Record #14 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Jul) ~ S [Jul]
    \\Record #15 - Error adding Attribute to member QTD(Jun) (3320)
    \\Record #15 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Jun) ~ S [Apr]+[May]+[Jun]
    \\Record #16 - Error adding Attribute to member QTD(Mar) (3320)
    \\Record #16 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Mar) ~ S [Jan]+[Feb]+[Mar]
    \\Record #17 - Error adding Attribute to member QTD(May) (3320)
    \\Record #17 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(May) ~ S [Apr]+[May]
    \\Record #18 - Error adding Attribute to member QTD(Nov) (3320)
    \\Record #18 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Nov) ~ S [Oct]+[Nov]
    \\Record #19 - Error adding Attribute to member QTD(Oct) (3320)
    \\Record #19 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Oct) ~ S [Oct]
    \\Record #20 - Error adding Attribute to member QTD(Sep) (3320)
    \\Record #20 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Sep) ~ S [Jul]+[Aug]+[Sep]
    \\Record #36 - Error adding Attribute to member YTD(Jan) (3320)
    \\Record #36 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD + S YTD(Jan) + S [Jan]
    \\Record #37 - Error adding Attribute to member YTD(Apr) (3320)
    \\Record #37 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Apr) ~ S [Qtr1]+[Apr]
    \\Record #38 - Error adding Attribute to member YTD(Aug) (3320)
    \\Record #38 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Aug) ~ S [1st Half]+[Jul]+[Aug]
    \\Record #39 - Error adding Attribute to member YTD(Dec) (3320)
    \\Record #39 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Dec) ~ S [1st Half]+[Qtr3]+[Qtr4]
    \\Record #40 - Error adding Attribute to member YTD(Feb) (3320)
    \\Record #40 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Feb) ~ S [Jan]+[Feb]
    \\Record #41 - Error adding Attribute to member YTD(Jul) (3320)
    \\Record #41 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Jul) ~ S [1st Half]+[Jul]
    \\Record #42 - Error adding Attribute to member YTD(Jun) (3320)
    \\Record #42 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Jun) ~ S [1st Half]
    \\Record #43 - Error adding Attribute to member YTD(Mar) (3320)
    \\Record #43 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Mar) ~ S [Qtr1]
    \\Record #44 - Error adding Attribute to member YTD(May) (3320)
    \\Record #44 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(May) ~ S [Qtr1]+[Apr]+[May]
    \\Record #45 - Error adding Attribute to member YTD(Nov) (3320)
    \\Record #45 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Nov) ~ S [1st Half]+[Qtr3]+[Oct]+[Nov]
    \\Record #46 - Error adding Attribute to member YTD(Oct) (3320)
    \\Record #46 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Oct) ~ S [1st Half]+[Qtr3]+[Oct]
    \\Record #47 - Error adding Attribute to member YTD(Sep) (3320)
    \\Record #47 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Sep) ~ S [1st Half]+[Qtr3]
    \\Record #2 - Incorrect Dimension [Year] For Member [ParentName] (3308)
    ParentName Consolidation DataStorage MemberName Consolidation DataStorage Formula
    \\Record #1 - Member name (Promotions) already used
    S Promotions S
    \\Record #2 - Incorrect Dimension [Promotions] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #3 - Member name (Promotions) already used
    Promotions S Coupon S
    \\Record #4 - Member name (Promotions) already used
    Promotions S Newspaper Ad S
    \\Record #5 - Member name (Promotions) already used
    Promotions S No Promotion S
    \\Record #6 - Member name (Promotions) already used
    Promotions S Temporary Price Reduction S
    \\Record #7 - Member name (Promotions) already used
    Promotions S Year End Sale S
    \\Record #2 - Incorrect Dimension [Payment Type] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #2 - Incorrect Dimension [Transation Type] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #22 - Member name (Home Entertainment) already used
    Home Entertainment + S Home Audio/Video + S
    \\Record #23 - Member name (Home Entertainment) already used
    Home Entertainment + S Televisions + S
    \\Record #24 - Member name (Other) already used
    Other + S Computers and Peripherals + S
    \\Record #25 - Incorrect Dimension [Product] For Member [ParentName] (3308)
    ParentName Consolidation DataStorage MemberName Consolidation DataStorage
    \\Record #26 - Member name (Personal Electronics) already used
    Personal Electronics + S Digital Cameras/Camcorders + S
    \\Record #27 - Member name (Personal Electronics) already used
    Personal Electronics + S Handhelds/PDAs + S
    \\Record #28 - Member name (Personal Electronics) already used
    Personal Electronics + S Portable Audio + S
    \\Record #31 - Member name (All Merchandise) already used
    Products + S All Merchandise + S
    \\Record #32 - Member name (High End Merchandise) already used
    Products ~ S High End Merchandise ~ S
    \\Record #33 - Member name (Systems) already used
    Systems + S Desktops + S
    \\Record #34 - Member name (Systems) already used
    Systems + S Notebooks + S
    \\Record #18 - Error adding Attribute to member Digital Recorders (3320)
    Home Audio/Video + S Digital Recorders + S
    \\Record #36 - Error adding Attribute to member Flat Panel (3320)
    Televisions + S Flat Panel + S
    \\Record #37 - Error adding Attribute to member HDTV (3320)
    Televisions + S HDTV + S
    \\Record #8 - Incorrect Dimension [Income Level] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #1 - Member name (Geography) already used
    S Geography S
    \\Record #2 - Error adding member 27425 (3317)
    \\Record #2 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    A M F GREENSBORO - NC S 27425 S 336
    \\Record #3 - Error adding member 36310 (3317)
    \\Record #3 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABBEVILLE - AL S 36310 S 334
    \\Record #4 - Error adding member 29620 (3317)
    \\Record #4 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABBEVILLE - SC S 29620 S 864
    \\Record #5 - Error adding member 67510 (3317)
    \\Record #5 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABBYVILLE - KS S 67510 S 316
    \\Record #6 - Error adding member 58001 (3317)
    \\Record #6 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERCROMBIE - ND S 58001 S 701
    \\Record #7 - Error adding member 42201 (3317)
    \\Record #7 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - KY S 42201 S 502
    \\Record #8 - Error adding member 21001 (3317)
    \\Record #8 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - MD S 21001 S 410
    \\Record #9 - Error adding member 39730 (3317)
    \\Record #9 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - MS S 39730 S 601
    \\Record #10 - Error adding member 28315 (3317)
    \\Record #10 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - NC S 28315 S 910
    \\Record #11 - Error adding member 79311 (3317)
    \\Record #11 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERNATHY - TX S 79311 S 806
    \\Record #12 - Error adding member 79601 (3317)
    \\Record #12 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABILENE - TX S 79601 S 915
    \\Record #13 - Error adding member 79608 (3317)
    \\Record #13 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABILENE - TX S 79608 S 915
    \\Record #14 - Error adding member 79698 (3317)
    \\Record #14 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    Are these errors due to data source, if yes what could be possible work around?
    Is there any problem with Essbase properties which I have set if so then when I validate cube schema why I dn't get any errors?
    Please help me, I am stuck here not able to deploy ASO Cube.
    Thanks in advance

    Hii
    I have the same problem , you have.
    did you manage to solve it ??
    Thanks in advance

  • Linking existing Essbase Cube to Planning

    My business team created an Essbase cube, and now they want us to link that cube to Planning.
    I opened an SR and I was told the following:
    1. Ensure you have a test environment to create this new Planning app before moving to production.
    2. Create a new Planning app in the test environment with the same name as the production Essbase cube.
    3. Export all Essbase data.
    4. Copy over the outline to the new Essbase cube in the test env. You can copy over the rest of the Essbase objects as needed (calc scripts, report scripts, etc).
    5. Import the Essbase data into the new Essbase cube.
    6. refresh Planning
    Everything went well except for Step 6. When I do the refresh from Planning, the Essbase Outline gets updated with the one from Planning which doesn't have anything since it was just created.
    I need to refresh the Planning Outline with the the one from Essbase that does have the data the users have been working on.
    Thanks.

    Hi,
    You will have to define all the dimension membes etc to Planning. Because Essbase is the database, it will be updated with planning information... There are no shortcuts.. But you can export your dimension members from existing Essbase and load into planning using HAL/ODI/DIM..
    Use outline extractor tool to get the existing dimensionality and create 1 metadata file per dimensions.
    I believe Oracle support thought that you want to create a new Essbase cube from existing Planning cube.
    Cheers
    RS

  • Unable to load data into Essbase cube using Essbase Studio

    Hi
    We are creating an essbase cube using Essbase Studio using flat files as data sources.
    We have taken different hierarchies into different flat files and created one fact file having dimension intersection along with data.
    We are able to create the cube and the hierarchy but not able to load any data.
    We are getting the following error
    Failed to deploy Essbase cube.
    Caused by: Unable to perform dataload from more than one flat file.
    Could anyone please help on this?

    Oh this was killing me, so I did this test in 11.1.1.3:
    1) Excel 2007 format -- no go, Essbase didn't see it
    2) Excel 2003 format, three sheets -- only the first sheet was read into an empty rule
    3) Excel 2003 format, one sheet -- the first sheet was read into an empty rule
    4) Excel 95 format, one sheet -- the first sheet was read into an empty rule
    The lesson?
    1) Excel 2007/2010 sheets don't work (no surprise there as the .xlsx format isn't supported).
    2) Excel 2003 and lower (hey, if you have Excel 4, I'll bet that works as well) work, but only the first sheet is recognized.
    Regards,
    Cameron Lackpour

  • Workspace error when drilling down on Essbase Cube

    An Interactive Reporting Service error has occurred.-Failed to acquire requested service.
    (2001)
    We're trying to create OLAP queries in IR to deploy through workspace. When I drill down on any dimension, after deploying to workspace, I get the generic error above. Has anyone seen this error?

    I have created one report using Essbase cubes in OBIEE11G and when I am archiving the same report at one local server and unarchiving it at some other server then at the other server I am facing this error.
    Any replies will indeed be helpful.

  • E-mail Alerts from Essbase Cubes

    Hi,
    I have Essbase 7.1.3 windows server and We do lots of Cube processing through Batch Files.
    I would like to have an option to send email alerts to the business users once we are done with the processing.
    Say for example , I have a Deposits Essbase cube and once i am done with the calculation and Enable connects to the users i would like to send a mail notification " The Deposit Cube now available....."
    Essbase have some thing called " Triggers..." But i am not sure how far will it help me.
    Looking forward for your inputs.
    Thnx,
    MS

    Okay, yes, I still use esscmd, so this example is for an esscmd script (some day I will convert them, I promise...).
    The shell (batch) script that I use calls esscmd to do the job, and then scans the script (using the for command) for tokens. These tokens determine who gets an email depending on the outcome of the script. By encoding the messaging into the script, I can control the business logic at an appropriate level. The TITLE token is also used during the notification, but I left the logic out that builds the SUBJECT variable (for brevity)...
    :TITLE Load Budget data to Daily Trends
    :Job Notifications:
    :ONERR [email protected]
    :ONERR [email protected]
    :ONSUCCESS [email protected]
    :ONSUCCESS [email protected]
    :ONSUCCESS [email protected]
    :ONSUCCESS [email protected]
    LOGIN "LocalHost" "<superuser>" "<superpassword>";
    ... etc.Here is the relevant part of the shell job that scans for tokens (the RESULT environment variable is set to either "ERR" or "SUCCESS" based on the output, with other variables set as needed):
    TYPE %SCRFILE% | FIND ":ON%RESULT%" >Notify.tmp
    FOR /f "tokens=2" %%a in (Notify.tmp) DO SendEmail -f %FROM% -t %%a -u "%SUBJECT%" -m "%MESSAGE%" -s %RELAY% -a %ATTACH%
    ERASE /Q Notify.tmp

  • Using ODI to load 2 similar Essbase cubes

    Hello all,
    I am trying to create an ODI routine that incorporates the following details:
    -Loads specific Essbase member properties from a single flat file to 2 similar Essbase cubes
    -The Essbase cubes are virtually identical, except that one is ASO and one is BSO, therefore the properties may differ for specific members (i.e. DataStorage, Consolidation, Formula, etc.). There are also other differences in dimensionality, but those details are inconsequential to this routine...
    -For each type of member property, the flat file has 2 sets of columns - one for ASO and one for BSO. Therefore, one column might be called "ASODataStorage" while another one is called "BSODataStorage". They have different values in them respective to the Essbase architecture.
    -There is also a set of columns called "ASOFlag" and "BSOFlag" that flag which members should even be loaded to that respective cube. So, one sub hierarchy may be needed for the ASO cube, but not the BSO cube.
    Earlier, I created 2 contexts for these cubes so I could use the same ODI routine and source metadata to update both cubes with a simple change of context. This part is working correctly. The challenge I'm facing now, however, is how to design a routine that will select the appropriate columns of data based on my context. Therefore, if one context is called "ASO", it should select the "ASO" columns and apply only those properties/members. And a similar situation should happen when the "BSO" context is created.
    I have tinkered with the idea of using a variable that stores the current context information, and becomes evaluated at runtime and then changes the source columns based on the variable value. However, I'm having trouble getting this to work correctly (I am a newbie to variables). I am also having trouble figuring out how to map all of the source columns to the target columns, as I am going from double property columns in the source to a single set of property columns in the Essbase metdata target.
    Is there a better way to approach this in ODI? Please note that I am aware that EIS can handle this as well...but I am looking for an ODI solution.
    Thanks in advance!
    -OS

    Hi,
    In simple terms you should be able to create a package, drag the variable on to the package and set the value as ASOflag
    Then drag your interface on to the diagram to run the ASO load (the interface should have a filter that uses the variable to filter the required records)
    Then drag the variable on to the diagram and set the value to BSOflag.
    Then drag your interface on to the diagram to run the BSO load (the interface should have a filter that uses the variable to filter the required records)
    Though you say you are changing contexts so you might have to go down the route of generating a scenario from a package for the ASO load, then a scenario for the BSO load, then create another package using the ODIstartscen tool and execute the scenarios with the specified scenarios.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • View Display Error in OBIEE with Essbase Cubes

    Hi All,
    Currently we are generating the Reports from Essbase Cubes.
    We have an hierarchy in OBIEE and when we are trying to drill down one hierarchy(Tech Executive) we are getting below Error.
    " Error
    View Display Error
    Odbc driver returned an error (SQLExecDirectW).
    Error Details
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Unknown Member [H1_Rel_TecExec_Ini_appl].[Unknown] used in query (HY000)
    SQL Issued: SELECT s_0, s_1, s_2, s_3, s_4, s_5 FROM ( SELECT 0 s_0, "Defect7M"."H1_Rel_TecExec_Ini_appl"."H1 Initiative Name" s_1, "Defect7M"."H1_Rel_TecExec_Ini_appl"."H1 Tech Executive" s_2, SORTKEY("Defect7M"."H1_Rel_TecExec_Ini_appl"."H1 Initiative Name") s_3, SORTKEY("Defect7M"."H1_Rel_TecExec_Ini_appl"."H1 Tech Executive") s_4, "Defect7M"."Defect7M#1"."Defect7M - measure" s_5 FROM "Defect7M" WHERE ("Defect7M"."H1_Rel_TecExec_Ini_appl"."H1 Tech Executive" = 'Unknown') ) djm "
    Can someone assist me how to resolve this error
    Thanks,
    SatyaB

    Satya,
    Have you done anything to modify the essbase drill logic within your BMM?
    Remember when modeling essbase you should just try to use the defaults first to ensure that all works correctly the first time through. Then you can adjust any hiearchies, federate, etc.

  • Problems in accessing Essbase cube using Interactive Reporting studio

    Hi All,
    I have developed a report in Interactive studio for which Essbase is the source. When i try to process my query i am getting the below error
    "Request [Report] from user[username] was terminated since it exceeded the time limit"
    Any idea as to how the time limit can be increased at essbase side.

    I still can not resolve the problem. I am pulling up an attribute dimension in my report and that seems to be the root cause of the problem. When i remove this attribute dimension and generate the report with rest of the details the report renders without any issues.
    can this be becuase the attribute dimension is "Dynamic Calc and Store" in Essbase cube and IR does not support certain essbase features such as Dynamic attribute dimensions ? This is quiet urgent and hence would need a quick response from ya'll

  • Combining relation facts with dimensions from an Essbase cube

    Hi!
    I am having trouble combining relational measures (from EBS) with dimensions from an Essbase cube. The dimensions that we want to use for reporting (drilling etc) are in an Essbase cube and the facts are in EBS.
    I have managed to import both the EBS tables and the cube into OBIEE (11.1.15) and I have created a business model on the cube. For the cube I converted the accounts dimension to a value based dimension, other than that it was basically just drag and drop.
    In this business model I created a new logical table with an LTS consisting of three tables from the relational database.
    The relational data has an account key that conforms to the member key of the accounts dimension in the Essbase cube. So in the accounts dimension (in the BMM layer) I mapped the relational column to correct column (that is already mapped to the cube) - this column now has two sources; the relational table and the cube. This account key is also available in the LTS of my fact table.
    The content levels for the LTS in the fact table have all been set to detail level for the accounts dimension.
    So far I am able to report on the data from the fact table (only relational data) and I can combine this report with account key from the account dimension (because this column is mapped to the relational source as well as the cube). But if expand the report with a column (from the accounts dimension) that is mapped only to the cube (the alias column that contains the description of the accounts key), I get an error (NQSError 14025 - see below).
    Seeing as how I have modeled that the facts are connected to the dimension through the common accounts key, I cannot understand why OBIEE doesn't seem to understand which other columns - from the same dimension - to fetch.
    If this had been in a relational database I could have done this very easily with SQL; something along the lines of select * from relational_fact, dim_accounts where relational_fact.account_key=dim_accounts.account_key.
    Error message:
    [nQSError: 14025] No fact table exists at the requested level of detail
    Edit:
    Regards
    Mogens
    Edited by: user13050224 on Jun 19, 2012 6:40 AM

    Avneet gave you the beginnings of one way, but left out that a couple of things. First, you would want to do the export of level zero only. Second, the export needs to be in column format and third, you need to make sure the load rule you use is set to be additive otherwise the last row will overwrite the previouse values.
    A couple of other wats I can think of doing this
    Create a replicated partition that maps the 3 non used dimensiosn to null (Pick the member at the top of the dimension in your mapping area)
    Create a report script to extract the data putting the three dimensions in the page so they don't show up.
    Use the custom defined function jexport in a calc script to get what you want

  • How to use the dynamical or static variable for ESSBASE cube name?

    Hi Experts,
    When I import ESSBASE Cube into physical layer, the cube name from ESSBASE is created automatically, such as H_Sales.
    I want to use the the static or dynamical variable for replacing the external name. So I try to create the static variable in RPD,such as cubeName, and use the following code
    'VALUEOF(cubeName)' into the textbox of external name.
    However, when I view the report in answer, it will generate the error message: Database VALUEOF(cubeName) does not exist.
    Is it possible to implement this functionality?
    Thanks..

    Hi,
    use <%=odiRef.getSchemaName("D")%>
    D as parameter if it is the Data Schema or W if you need the schema from Work Schema
    Your command will be like:
    select <%=odiRef.getSchemaName("D")%>.GER_LOT_EXEC_ODI('Fluxo', 1, 'C') FROM DUAL
    Works?
    Cezar Santos
    http://odiexperts.com

  • Issue in integrating Essbase cubes with OBIEE

    Hi
    I am trying to use Essbase cubes as datasource in OBIEE for generating reports,but the issue is in generating , No columns in fact table of cube in BMM layer.
    Outline of cube is
    Revel(cube)
    (Hierachies)
    Time Time <5> (Label Only)
    Item <54> (Label Only) (Two Pass)
    DepInst <20> (Label Only)
    SFA_Flag <2>
    Deduction_Flag <2>
    Rating_Category <6>
    PD_Band <9>
    Product <17>
    Entity <4>
    CR_Agency <5>
    I am confused how to generate reports without measures in fact table.
    Regards
    Sandeep

    Hi Sandeep,
    in that case it's as I thought:
    Or did you just not specify any measure hierarchy?You tried this...
    In BMM layer i made this dimension as fact and tried to create reports but not use....which isn't the way. First of all your cube seems to be built quite bizarre since it doesn't even provide a default measure hierarchy so I'd have your Essbase guys check that.
    As for the OBIEE side: the key is the physical layer. BMM's already too late. In the physical cube object, you must define one of the hierarchies as the measure hierarchy (since your cube doesn't seem to provide it; see above):
    [http://hekatonkheires.blogspot.com/2010/02/obieeessbase-how-to-handle-missing.html]
    Cheers,
    C.

  • Cannot Lock and Send data to an Essbase cube

    Hi all,
    One of our customer is executing a Macro script to lock and send data to the essbase cube from an excel sheet.
    They reported that in several cases where users will submit their data, and later discover that their changes are not in Essbase.
    The calls to EssVRetrieve (to lock the blocks) and EssVSendData are both returning successfully and there is no error message received while executing the above macros.
    I reviewed the application log file and found the following message:
    [Mon Nov 24 18:59:43 2008]Local/Applicn///Warning(1080014)
    Transaction [ 0xd801e0( 0x492b4bb0.0x45560 ) ] aborted due to status [1014031].
    I analysed the above message and found the user is trying to lock the database when already a lock has been applied to it and some operation is being performed on it. Because of that the transaction has been aborted. But customer says no concurrent operation is being performed at that time.
    Can anyone help me in this regard.
    Thanks,
    Raja

    The error message for error 1014031 is 'Essbase could not get a lock in the specified time.' The first thought I have is that perhaps some user/s have the 'Update Mode' option set in their Essbase Options and thus, when they are retrieving data, they are inadvertantly locking the data blocks. If that is the case, you will probably see this issue sporadically as the locks are automatically released when the user disconnects from Essbase.
    To make it stop, you will have to go to every user's desktop and make sure they have that Essbase Option turned off. Further, you will have to look at any worksheets they may use that may have an Essbase Option name stored on it. The range name is stored as a string and includes a setting for update mode. Here is a sample that I created for this post where I first turned 'on' update mode and then turned 'off' update mode:
    A1100000001121000000001100120_01-0000
    A1100000000121000000001100120_01-0000
    Note the 11th character in the first string is '1' which indicates that Update Mode is 'on'; in the second string, it is 'off'.
    This behavior, particularly with update mode, is the only one of the behaviors that I disliked in Excel and pushed me to design our Dodeca product. In Dodeca, the administrator controls all Essbase options and can either set individual options to the value they want or they can allow the user to choose their own options. Most of our customers do not allow the user to set update mode.
    Tim Tow
    Applied OLAP, Inc

  • Update member  count error for essbase cube

    Whenever i import a cube from essabse into obiee. i get the following error when i click on "update member count" on any member in the Physical layer of the obiee administration.
    this problem comes even if i import a different cube, meaning this is not due to essbase error.
    [NQODBC][SQL_STATE:HY0000][nQSError: 10058] A general error has occurred.
    [nQSError:43093] An error occured while processing the EXECUTE PHYSICAL statement.
    Essbase Error: Unknown Member Measures.xxxyyyxxxCount used in query
    kindly help!!

    i am using version 11.1.1.3
    i have created an holap cube in Essbase integration services. i have created olap model using rdbms source in the EIS. however i am unable to access the rdbms level(hybrid analysis enabled) data of the essbase cube in obiee.

  • How to make data in Essbase cube equal to data in DW when drilling through

    Is there standard ways in Oracle BI + Essbase to make data in Essbase cube and DW equal (corresponding)?
    For example when we are drilling down from cube to DW in this moment in DW may be loaded additional data (new data) which are not loaded in the cube yet.
    So we have situation where data in the cube not correspond to data in the DW.

    I think rebuilding the cube on a more frequent basis not solves the problem – there will be significant time between the moment when data loaded in DW and when data updated in the cube.
    I thought of creating 2 tables in DW (“new” and “old”) and 2 cubes (“new” and “old”).
    So the process of loading data will look like this:
    1. We have corresponding data in table “old” and cube “old”. User always works with “old” objects.
    2. Load data to table “new”.
    3. Load data to cube “new” from table “new”.
    4. Rename tables and cubes: “old” to “new”, “new” to “old”. Here users starting to work with updated cube and table.
    5. Add new changes go cube and table “new” (there will be old data).
    6. Go to step 2.
    But this way is too expensive (storage amount doubles).
    And maybe easier way can be found?...

Maybe you are looking for