Drill Through in EIS

I am having an issue with EIS metaoutline. Below is my scenario,
We have a metaoutline for drillthrough from ASO cube with multiple hierarchies enabled. So by default the dimension becomes 'Label Only' and the dimension data value is inherited from the first member under the dimension. So when the cube retrieval is done the value of the dimension is displayed as the value of its first child but when a drill through report is launched at the dimension level the result is the sum of all the members under the dimension. I have the dimension marked as label only in metaoutline and changed the consolidation for only the first rollup as '+' whereas others as '~' but still for some reason the drill through SQL is considering everything. Is there anything I am missing on this design which I am not aware of or is it a known issue in EIS?

I haven't used EIS for a while, but I would be surprised if drill-through cares about consolidation properties. You might be able to work around it by using custom SQL with a CASE condition on the top-level member.
That said (not sure which version you're on), the 9.3.3 release notes for EIS (http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/eis_93300_readme.pdf) state: "When working with drill-through reports for alternate hierarchies, you must create a separate drill-through report for each hierarchy."

Similar Messages

  • Enabling Drill Through causing Essbase Integration Server hang.

    During the automation process using olapicmd command and *.cbs we are enabling Drill Through which is causing Essbase Integration Server hang.
    We don't get any error message in log file. Plus sometime its run successful , also when we run this manually going to EIS console, it run fine.
    Thanks in advance
    -Piyush

    Hi Kishore,
    Thanks for your prompt reply......
    I have checked in before itself the Drill down option ......
    I am not able to understand whats the issue we are able to drill through in EIS till last level but after improting in OBIEE we are not able to drill through to last level, in the last level it showing no results....
    I am not able to find the solution any other suggestions ?
    Regards,
    Tarang Jain

  • How to filter records in EIS drill through using template SQL

    Hi,
    I'm looking for an option to filter records in EIS drill through using Template SQL.
    For eg: If we user runs drill through on 2011, it should restrict display of Jan & Feb and should display records for other months.
    I tried using NOT IN clause, but got an error.
    Can any one help me in understanding how this needs to be defined in template SQL
    Thanks in advance

    Hi Glenn,
    I'm able to filter the records for specific periods.
    However, I'm facing another problem now.
    When I try to run drill through I get 'OLAP_error (1192025): Unknown Error: Not a valid Entry' error.
    This is happening when I include condition as ((($$ab.ACCOUNT_CODE-COLUMN $$) IN ($$Account-VALUE$$)))
    Here, ACCOUNT_CODE is field from Account dimension table and 'Account' is the name of the dimension.
    If I remove this statement and run drill through, it runs but shows data for all accounts (irrespective of the Account selected)resulting in incorrect data.
    Our RDBMS is Oracle. Can you please help me with this
    Thanks

  • EIS drill through report build

    Hi,<BR><BR>I want to create multiple drill through reports using EIS. But looks like I need to create all the required reports before I build and load the cube. Once I have built the cube using EIS, I cannot go in the metaoutline and add new drill through reports. Is this true, or am I missing something? <BR>So whenever I need to add new reports for drill through, do I need to build the cube all over again?<BR><BR>Thanks<BR>RMP

    No, you can open your metaoutline and build your drill through report and then run an update that just refreshes the drill through reports without having to rebuild or reload the cube.

  • EIS Drill Through Essnet error message.

    We are using EIS to anable drill through from Excel. I've just set up some new drill through reports, and they work fine except when you try and drill through at GEN 1 on a particular sparse dimension. The dimension isn't specified in the "OLAP intersections Levels" as we want the report to show all results for that dimension.
    The error message that gets returned is {ESSNET MESSAGE} - in a box with ESSDTU in the left hand corner.
    Thanks
    Paul

    You are saying the dynamic query was generated, did you copy the query and tried to execute it in the database client. Check the SQl for any errors and also in the did you see any SQL errors?

  • EIS Drill through reports should be disabled at #MISSING data cell

    Hi,
    I have working on Oracle Essbase Integration server(EIS) 11.1.1.3. I have developed the 2 drill-through reports.
    Every thing is working fine. Using smart view, users are able to access the drill-through report.
    As an another requirement, if there is no data(#MISSING) for any member combination in Essbase, Drill through report should not be enabled for this combination in smartview at retrieve.
    How can I handle this requirement? In OLAP Intersection levels, only dimensions’slevel/generation can be specified.
    Please help me on this. It is very urgent for us. Quick help will be highly appreciated.
    Thanks & Regards,
    Mohit Jain

    Hi Gary,
    I think its the latter. I've been asked on more thant one project to code things that prevent users from doing things that otherwise wouldn't make sense to do. Within the last year I was actually asked to configure things "as if I was providing functionality for 2 ^nd^ graders". At least, based on experience, this is how I relate to the OP's request.
    I agree, its absolutely silly (and frustrating ) that users would try to drill through on a #missing cell and not see anything. What's worse, depending on where the drill through goes, and how its set up, users might drill on #Missing and actually see data! Yikes! Now in an experiential sense, the users can expect to see data where data ought not be.
    So sometimes its just easier to just remove the button altogether than to have to explain when and why it can be used, and why when it's not used that way it did what it did. And users being part of the driver behind project requirements, don't want to hear "because you're not supposed to".
    Hopefully the OP will clarify and we can provide what s/he's looking for.
    regards,
    Robb Salzmann

  • EIS Drill Through Reports

    Hi,
    Working with Drill Through reports on essbase 9.3.1. I have defined 10 drill thru reports in EIS because of mulitple hierarchies in some dimensions that needed to be specified. I created 1 from scratch and then copied it and modified OLAP intersections as needed, typically it was just 1 dimension that I needed to delete and re-add using a different child.
    Some simple drill thru retrievals are working just fine, while others are causing me to receive an error...
    {ESSNET MESSAGE} Network error [10054]: Cannot Send Data
    Why would some report retrievals work, and others get this message?
    Any ideas?
    TIA,
    Robert

    Not a problem.. http://timtows-hyperion-blog.blogspot.com/2007/12/essbase-api-error-fix-geeky.html
    Remember, you have to reboot the machine(s) where you make changes for them to take effect.. If your EIS server is also Windows (and on a different server), do the same thing there.
    We see this issue all the time with the Outline Extractor as it makes many, many requests to the Essbase server (and each one uses a port that is not released by Windows for some time).. In fact, I am currently writing some new caching functionality into our Dodeca-Essbase server and am putting a configurable delay into the code so the code doesn't call the server too quickly (but, of course, this is something that runs in the background, so performance isn't a huge issue in that case)..
    Let us know if it fixes your issue.
    Tim Tow
    Applied OLAP, Inc

  • EIS drill through reports in Analyzer

    I'm having trouble pulling SQL drill through reports defined in EIS when using Analyzer. I can pull the report when I'm in Excel, but when I go into Analyzer and double click, I get the related content box to open, but no links to the drill through report.<BR><BR>I did some searching on the Hyperion support site and found an entry in the knowledge base that said the Grid API option had to be turned on for this functionality to work. Of course there was no mention of how to turn the Grid API on and I have not been successful in finding anything in the install guide or the admin guide.<BR><BR>I'm using Essbase 7.1.5 with EIS 7.1.2 and Analyzer 7.2.5.<BR><BR>Is anyone using Analyzer to successfully pull EIS drill through reports?<BR>Did you have to turn on the Grid API option?<BR>How is this feature turned on?<BR>Or, any other suggestions?<BR><BR>TIA

    <p>Hi,</p><p> </p><p>I am also facing few issues related to AIS:</p><p> </p><p>I am unable to use Drill Through</p><p> </p><p>(1) Smart View: It is asking for Connections and i am unable toprovide Shared Services Provider Information. It throws an error.In case i use URL as add feature then it asks for credential butstill no luck</p><p> </p><p>(2) Then i tried to used Add-In Excel and (This is my 1st time):When i double click on the data figure based on Intersaction leveli defined, it is taking me LRO's and now i don't know hoe toproceed further</p><p> </p><p>Can anybody help me?</p>

  • Drill-Through Reports using EIS

    Hello -
    Is there a document to guide us through the steps to create drill-through/Hybrid Analysis reports using EIS 9.3.1? I couldn't find it in sysadmin or dataprep documents ..
    Thank you!

    You can check in EIS document however producing drill through report is fairly straight forward. Select Tools -> Drill Through and then design SQL which you want to execute. I don;t have tool access so can;t give exact steps.
    Let me know if you have any issues.
    Thanks,

  • Drill-Through reports in EIS 7.1.X

    Hi,<BR><BR>We had some problem migrating to EIS 7.1 from 6.5.4. EIS seems to ignore all the dimension tables defined in the model whenever executing the drill-through reports, and only using fields in fact table in the "where" clause. The same report/"intersection points" works perfectly in 6.5.4.

    <p>Hi,</p><p> </p><p>I am also facing few issues related to AIS:</p><p> </p><p>I am unable to use Drill Through</p><p> </p><p>(1) Smart View: It is asking for Connections and i am unable toprovide Shared Services Provider Information. It throws an error.In case i use URL as add feature then it asks for credential butstill no luck</p><p> </p><p>(2) Then i tried to used Add-In Excel and (This is my 1st time):When i double click on the data figure based on Intersaction leveli defined, it is taking me LRO's and now i don't know hoe toproceed further</p><p> </p><p>Can anybody help me?</p>

  • *****EIS : Drill through Report Error while excel data retre

    Dear All,
    could you please help me in the below error . When i tried to get the drill through reports in excel add-in ,
    i am getting the below error . When i had look into EIS log, its generating dynamic query for this drill through reports .
    [NCR][ODBC Teradata][Teradata Database] Syntax error- expected something between the word '<<Databasename>>' and the word 'ai'.Unable to get catalog string.
    Thanks in advance .
    M

    You are saying the dynamic query was generated, did you copy the query and tried to execute it in the database client. Check the SQl for any errors and also in the did you see any SQL errors?

  • EIS Drill-Through to Transactional Data

    Hi!Is there a quick way to retrieve transactional fact data(non-summarized)from the fact table when drilling through in the Essbase Spreadsheet Add-in ? Have set up a drill through report through EIS, but it doesn't retrieve fact table columns even though the Template SQL was modified. Thanks in advance

    We have two SQL tables, Detail and Summary. In EIS, our Model has both tabels joined as the fact table. When you create the Drill Thru report you select the fields from the Detail table but the SQL logic still looks at the summary table. Note for excel, when you drill thru make sure each record in detail is unique or excel will suppress. we had to add a field to get all record to display in excel.

  • Template SQL for EIS Drill-Through

    I am trying to figure out the command that I need to add to my template SQL in an EIS drill-through report that will exclude all rows that have a 0 value in my data column when the report is executed. Does anyone have an example of how this can be done?

    The $$dimension-COLUMN$$ represents the column that contains your member name in your table and the $$dimension-MEMBERCOLUMN$$ represents the member.
    When you run the drill-through report the $$dimension-MEMBERCOLUMN$$ will be replaced by the member referenced in the cross-section.
    e.g. if you launch your drill-though on a cell where the product ID is 100-10 then the drill-though will only pull out data for product 100-10
    SELECT......WHERE SKU IN (100-10)
    Gee

  • EIS 6.5.1 Drill through Reports - Urgent

    Hi all, Is there any limitaion on number of fields in the EIS drill through reports. It seems it accepts only 10 columns, rest of the column data is not properly displayed. Please update me on this.thanksSels

    We ran into this problem a while ago. It seems that after 10 columns, formatting get really odd. We submited it as a bug a number of months ago.Glenn S.Narratus [email protected]

  • EIS 6.5.1 - Drill through report

    Hi all,Is there any limitaion on number of fields in the EIS drill through reports. It seems it accepts only 10 columns, rest of the column data is not properly displayed.

    We ran into this problem a while ago. It seems that after 10 columns, formatting get really odd. We submited it as a bug a number of months ago.Glenn S.Narratus [email protected]

Maybe you are looking for