EIS, ASO & Drill-Thru

How are EIS drill-thru reports exposed to the user in an aggregare storage (ASO) database if linked reporting objects (LRO) are not supported?

Ok, I found if I add
HISLEVELDRILLTHROUGH application_name
to my Essbase.cfg file It at least recognizes that there are reports out there, Now I just get an odd error:
" Invalid selection. All selected data cells must be contiguous. Selected cells can span multiple members in one dimension only. Selected cells must share a common parent and must come from same relational column."
It's interesting it worked on an older version of EIS, just after migration, it stopped working

Similar Messages

  • EIS drill thru

    I'm trying to do a drill-through (Thru) report in EIS and can't get it to show up in the Excel add-in. I've tried all sorts of combinations of intersection levels and columns in the report creation. I have drilled to the bottom of all of the dimensions in excel, but the reports still won't show up in the linked object browser. I'm on version 7.1.6 of both EIS and Essbase.
    Has anyone run into this before. I even tried recreating the model and metadata outline in case of corruption.
    There is another EIS built cube on the server with a drill-thru report and it runs fine. Any suggestions?

    Ok, I found if I add
    HISLEVELDRILLTHROUGH application_name
    to my Essbase.cfg file It at least recognizes that there are reports out there, Now I just get an odd error:
    " Invalid selection. All selected data cells must be contiguous. Selected cells can span multiple members in one dimension only. Selected cells must share a common parent and must come from same relational column."
    It's interesting it worked on an older version of EIS, just after migration, it stopped working

  • Excel is not showing multiple Drill thru report selection option

    We have created 3 drill thru reports in EIS, excel is not showing Select Drill-Through Report Dialog Box when tying to acess drill thru reports. It defaultly executes the first drill thru report, we want it to list the available reports so that we can select accordingly after view/launch is selected.
    essbase 7.1.6 version SQl server 2000

    Hi,
    This Prompt message would have been set in WAD(XHTML Coding section) in your old project. Now , you cross check your Web template for the same. Your issue will be resolved.
    Regards,
    Suman

  • "XML Load error: An invalid character was found in text content" Drill Thru

    Hi,
    I am using Smart View, 2007 ms office.
    We are using EIS to have Drill Through reports.
    When I select the particular intersection and click on Hyperion --> Adhoc Analysis--> Drill Through Reports,
    Drill Through selection window is opening but when click on Launch/Execute.
    It throwing below Error
    "XML Load error: An invalid character was found in text content"
    This error is showing only some intersections...some other intersections are working fine.
    The same intersection if retrieve from ESSBASE --> Addins--> linked objects, Drill thru reports are showing fine.
    From Excel Addins everythg working fine.
    I tried in 2003 MS office from my colleague system. the same error.
    "XML Load error: An invalid character was found in text content"
    Please someone help me....!
    Regards,
    Rajendra Prasad Gella.
    Edited by: Rajendra Prasad Gella on Jun 10, 2010 4:26 AM

    This type of Issue does not happen using Excel Add-in but Smart View. We encountered it as well. I have a feeling the root cause is the ESSLANG which used to be selected during installation. If the Essbase has for instance "English Latin1" or "English US Ascii Binary" and the client does not have it, then this would occur.
    We had old SR on it because we were testin the APS 7.1.6. SR 2-603906: Excel Essbase Add-in splitting special characters such as the " ü " in. Whe we reinstalled and selected same ESSLANG as Essbase server the isue stopped.
    We did not have to chnage our code to scrub out ant special characters. !
    Jullin

  • Essbase studio drill thru report Test error

    Hi All,
    Essbase studio drill thru report is producing the below error: Unable to retrieve drill thru result.
    Error in the select statement. Line = 2466.
    Error in query execution. Please review the query and try again.
    Cannot execute a SQL query
    ORA-01791: not a SELECTed expression
    Any idea... i am able to test for some of the dimensions but this error is coming for a few dimensiosns .... i verified all the joins between dimensions and facts.. everything is fine.
    Thanks,
    Praveen

    Hi Glenn,
    This is a test report executed with in Studio console. Yes, i did verify the generated sql by studio server and was able to drill down to the detail. I dont find any information in the logs when testing this. Probably, i would need to increase logging level. Will do that and update here if i dont find much help there.
    Thanks,
    Praveen

  • Essbase Studio drill thru report error

    Hi All,
    Essbase studio drill thru report is producing the below error: Unable to retrieve drill thru result.
    Error in the select statement. Line = 2466.
    Error in query execution. Please review the query and try again.
    Cannot execute a SQL query
    ORA-01791: not a SELECTed expression
    Any idea... i am able to test for some of the dimensions but this error is coming for a few dimensiosns .... i verified all the joins between dimensions and facts.. everything is fine.
    Thanks,
    Praveen

    Hi Glenn,
    This is a test report executed with in Studio console. Yes, i did verify the generated sql by studio server and was able to drill down to the detail. I dont find any information in the logs when testing this. Probably, i would need to increase logging level. Will do that and update here if i dont find much help there.
    Thanks,
    Praveen

  • Hyperion Analyzer Drill thru issue

    hi
    I have some drill thru reports attached to the one of the cubes. I am using hyperion analyzer for reporting. When i am putting more than one filter from same dimension i am getting below error and drill thru not working.
    All selected data cells must be contiguous. Selected cells can span multiple members in one dimension only. Selected cells must share a common parent and must come from same relational column.
    The drill thru reports are working for some combination of filters but some other combination it is not working(here the combinations are siblings in outline). Even i saw if i put a filter with child and parent combination the same error coming.
    I am not able to figure it out what is the cause? Any help/suggestion wll be of great help.
    TIA

    Di you get solution for above problem .Please update

  • Essbase Studio Drill-thru security

    I applied a filter in Essbase so a user had filtered access. In Smartview I retrieve data and properly gett the NoAccess message, so far so good. If I do a drill-thru. It drills to the data in my report. I would think IT should prevent drill-thru from occuring. Am I doing something wrong? I don't think it should work this way.

    Hi Glenn,
    This is a test report executed with in Studio console. Yes, i did verify the generated sql by studio server and was able to drill down to the detail. I dont find any information in the logs when testing this. Probably, i would need to increase logging level. Will do that and update here if i dont find much help there.
    Thanks,
    Praveen

  • FDM Drill thru to Planning

    Can I load the data in planning for the dimension that is not existing in planning but when i drill thru from Planning i should see the detailed data.
    For e.g.HR Deptt->Salary in Planning
    now wen i m loading the data thru FDM it is Employee->Salary->HR
    so wen i drill down i shud see the employee details
    Can we achieve something like this in FDM...Please help....If yes let me know the functionality through which this can be done..
    Thanks

    If you bring in a source dimension like employee, you will need to map it to some target. However, you could import into one of the attribute dimensions and then you would not be required to map to a target. When you drill through, you could see these attributes.
    So the short answer is yes you can do this.

  • Filters for Drill thru reports

    Can we make the filter available for all users in a drill thru report?
    Thanks
    Kannan.

    Maaguiar,We have Analyzer 6.1.1 installed within WebSphere Unix running AIX 4.3.3 We have been told by Hyperion support that this is a bug. No confirmation has been made yet as to whether this will be fixed in version 6.2 which has a RMF date of late October

  • SQL Drill Thru (v502p13a) and Excel Client(V6.1.5):  Formatting  Sucks

    Sorry about the last note, caffeine got me a little jumpy!I got the SQL Drill through working rather well. Fast, efficient, and the users like it. (I guess I keep my job for another week or so). Anyway, the format of the returned data is brutal. It is text, and nothing can be done in Excel to change the format. The field's datatype is decimal (15,2) and the data is number formatted from the high priced ERP system. So, of course, it makes no sense to me.Any workarounds out there? One thought. The SQL Drill Thru has a section where you can add a pre or post connection .dll. Maybe something there with formatting capabilities would resolve. We do NOT utilize Hyperion Intergration Server.Any suggestions would be appeciated. [email protected]

    I don't recall if it was an option in the Essbase 5 client, but if you could create a VBA macro to invoke the SQL Drill through rather than using the Add-In menu, then you could build some macros to clean up the format a little.Other than that, I'm not sure what (easy) solution there would be.Regards,Jade------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

  • EIS - Essbase drill though issue

    Hi
    We are using Essbase 11.1.2 with EIS to build our BSO cube, and provide drill through to a SQL server database
    Our drill-through has been working OK but now we have an issue where it stops working for a small number of cost centres
    We get the first drill through panel for all cost centres (thedialog box that says : Linked object Browser, with oprions to 'View/Launch' etc), then, upon selecting 'View/Launch',  for most Cost Centres we get a list a list of pre-written queries, but for a subset of cost centres we get 'There are no reports defined for the selected intersection'
    Our BAU process is to reload our dimensions from files and then update the drill through in EIS , which we do several times a week
    Anyone got any ideas why it should stop working only for certail cost centres   ?
    Thanks

    Since I made the post I have explored some more.  The SQL statements for the drill-though report definitions work with all cost centres, when I run them in a SQL console (SqlServer management console). But even when I create a new drill though report, it still only works only for the cost centres that previously worked successfully with the existing drill through reports.  There is no signifigant difference in Essbase between the cost centres that work and the ones that dont , so I am completely stumped
    HELP !

  • EIS and Drill Through Report Video

    Hello,
    If you want to learn Essbase Integration Service and Drill through report features, here is the videos tutorial of 2 hours.
    EIS & Drill through : http://www.box.net/shared/qlj6ba8gf3
    Amit
    learnhyperion.wordpress.com

    Hi,
    I could not play the movie. Which player is suitable to run the movie?
    Thanks in advance

  • ASO Drill down problem needing desperate help

    In Excel addin and Financial Report, I have problems with drilling down. We're using Essbase ASO 9.3.1.
    The scenario is as follows:
    Parent 　Figures
    z 　　
    　z1 100
    　z2 200
    　z3 300
    1. When I retrieve in Excel or FR for z, I get 600 which is corrent.
    2. When I retrieve in Excel or FR for z1 or z2 or z3 or all together, I get correct figures.
    3. When I retrieve in Excel or FR both parent and child, z = 600, z1 = 100, z2 = 200, z3 = 300, I still get correct figures.
    Problem:
    When I drill down from Excel or FR from a, which had correct figures, z1 = 100, z2 = 200, z3 = 300, will be correct but z will be missing (z = missing).
    Is there anyway so that I can drill down from z and still having all figures correct like I get in point 3.?
    Similarly I found a post as follows, which has similar problems:
    ASO retrieves inconsistent between Excell and Finanical report in 9.3.1
    The difference is that my Excel does not display parent as well when drilled down.
    Edited by: sycshk on Dec 22, 2008 2:14 AM

    Hi Anjana,
    Check your DSO setting was checked for SID generation upon activation or not. If it unchecked then your report will run very long time because of no indexes.
    Try your report with the fields you are drill down indefault view and see how much time report is running. So you will know whether it is dril down problem or huge data problem. Try to keep as many as filters as per user.
    Thanks.

  • SQL generated by EIS for Drill Through

    Hello,<BR>We are currently using EIS 7.1 on AIX. When we run a drill through report on a large flat dimensional member there are two separate SQLs generated. The first SQL has a where condition with appx. half of the child members and the second one with second half. Is this due to any kind of limitation on he length of the SQL generated?<BR>If so is there any way to work around with this?<BR>THanks a lot in advance<BR>Kris

    Hi Michael,
    I have got the following inputs from the OLAP forum on this query:
    P_S
    Posts: 40
    Registered: 5/29/07
    How to see the SQL (OLAP DML) generated by Discoverer for OLAP
    Posted: Aug 30, 2007 9:30 AM Reply
    Hi,
    I originally posted this query on the Discoverer forum, but it was then suggested to post it here in the OLAP forum. Please help.........
    Is there a way to see the SQL (OLAP DML) generated by Discoverer for OLAP (the way we have "View SQL" in Discoverer Relational). The version in use is 10.1.2.48.18.
    Thanks,
    Piyush
    KLaker
    Posts: 1,341
    From: Manchester, UK
    Registered: 1/10/01
    Re: How to see the SQL (OLAP DML) generated by Discoverer for OLAP
    Posted: Sep 5, 2007 7:34 AM in response to: P_S Reply
    Directly within Discoverer for OLAP (or Viewer)? No - because there is no way to change the behaviour of the generated SQL, you cannot add hints or create any MVs to change the SQL generated. You can trace the SQL generated during a Disco for OLAP query though by switching on some of the OLAP tuning and diagnostic features. There is more information contained in the Discoverer for OLAP Best Practices Guide:
    http://www.oracle.com/technology/products/discoverer/pdf/discoverer_plus_olap_best_practices.pdf
    Keith Laker
    Oracle EMEA Consulting
    BI Blog: http://oraclebi.blogspot.com/
    DM Blog: http://oracledmt.blogspot.com/
    BI on Oracle: http://www.oracle.com/bi/
    BI on OTN: http://www.oracle.com/technology/products/bi/
    BI Samples: http://www.oracle.com/technology/products/bi/samples/
    Regards,
    Piyush

Maybe you are looking for