EIS Template SQL Drill through

Has anyone been able to successfully use the template SQL drill through option in EIS? It seems that any modification to the default code only results in the error message "No display columns defined for a selected report". Maybe I'm missing something fundamental but can't get anything from the limited documentation. Without the paramaterization clauses, the SQL executes fine in a native query tool.

Maybe I could state my issue another way.
The reason I wanted to pass a data value to the drill through report is to utilize the Filter security defined in Essbase. If the user has access to an intersection point that has data, then the drill through should execute.
The security hole is when a user doesn't have access to an intersection point, they can still execute a drill through report and get to the detail. This does require a sophisticated user. I know you can apply security to the SQL data source and require a log in with the drill through, but I was hoping to avoid that mess.
Thanks,
Scot

Similar Messages

  • SQL Drill-through Password Update

    Hello! Is it possible to use a script to update the password defined for the SQL Drill-Through? Our security policy does not allow the use of graphical user inteface at the production environment (Integration Services Console)... And we have to change the passwords monthly...<BR>Thank you!

    You can have a "drill thru" defined to give you a view of lower level data that is not stored in your essbase cube.<BR><BR>For example you may store only employee numbers in your essase cube, but from time to time you may need to know all details of an employee. You would setup a drill-thru using employee number to hit an SQL database and find all details for that employee (using the emplyee number).<BR><BR>Its basically just a method of showing very low level data which would not be stored in a cube.<BR><BR>You can define the drill through's using EIS.

  • SQL Drill through??

    I am new to the Essbase world. We have a few business requirements that requires us to report on a flat measure (it does not make sense to be a part of the cube as it can not be aggregated across dimensions) along with other measures from the cube. We were thinking about doing a drill through to relational db.We do not have integration server installed. The server options on the Application manager indicate that we have SQL Drill through & SQL interface options. But what I am not sure is how to specify a measure as drill through & how would I be able to drill through a specific relational table. Could some one tell me if I can do this without HIS? Any ideas or suggestions would be greatly appreciated.Thanks,Nithya

    with vba, you can easily issue a sql query on a relational data source base and have the results placed in it's own sheet. (for free)look under ado (access data objects) in programming references for vba or vb.If you have any vb programmers in house, they could set something up for you in minutes.This is an often overlooked method of retrieving relational information based on the multidimensional criteria from an Essbase report.howard314-406-4022

  • EIS - Fact Tables, Drill Through Reports & User Defined SQL

    I have built a model using two factables. (Virtually one table as the two are combined in the OLAP Model.) I then built my metaoutline and I have specified an ASO cube. I built the cube and the drill through reports and then tried to load the cube.
    Intially the standard SQL generated no records. I tweeked it a bit and it then loaded. However, once I tweeked the SQL I could not get any drill through reports.
    Does anyone know how the SQL for the drill through reports is populated? Does it run off the user defined SQL?

    I've figured it out. FYI to those curious.
    The SQL for the drill through reports are specified on how the model is set up. The User Defined SQL is only for the data load.

  • EIS + template SQL

    Hi,
    Can any EIS (11) expert could confirm what CHM doc says regarding building drill-through reports using template SQL.
    "(...) you cannot use the $$ substitution variables in template SQL when (...) the dimension is built from a *parent/child* table."
    Which means that if my dimension tables in my EIS model are built on a parent-child way then the $$ substitution variables won't work?
    I'm cursed
    Edited by: sroux on Jun 7, 2011 3:39 PM

    Thanks Glenn,
    So you mean that YES I can implement drill with parent child based fact tables using $$ variables.
    However and as I said in the prevoithis is what I can read in the doc :
    +"Integration Services template SQL uses the "$$" syntax as the variable delimiter. All text contained within the "$$" syntax is replaced with actual column or data values during drill-through execution. However, you cannot use the $$ substitution variables in template SQL when the intersection level of the dimension is defined at Generation 1 and the dimension is built from a parent/child table."+
    Now I've been in the EIS doc regarding these blooding $$ substitution variables and cannot make it work.
    What is the difference between :
    $$dimension-*$$COLUMN$$* & $$dimension-VALUE$$
    $$dimension-*$$MEMBERCOLUMN$$* & $$dimension-MEMBERVALUE$$
    For instance this is not working :
    SELECT DISTINCT aa.ANNEES as ANNEES, aa.CLIENTS AS CLIENTS, aa.RESPONSABLES as RESPONSABLES, m.ALIAS as MOIS, i.ALIAS as NATURES, SUM(aa.MONTANT) as MONTANTS
    FROM RPNDBO.FACT aa, RPNDBO.MOIS m, RPNDBO.INDICATEURS i
    WHERE
    *$$MOIS-COLUMN$$ = $$MOIS-VALUE$$ and $$INDICATEURS-COLUMN$$ = $$INDICATEURS-VALUE$$* and aa.ANNEES = 'A2010'
    GROUP BY aa.ANNEES, aa.CLIENTS, aa.RESPONSABLES, m.ALIAS, i.ALIAS
    ORDER BY 1 ASC, 4 ASC, 6 ASC, 5 ASC, 2 ASC, 3 ASC

  • 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 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 report Intersection levels

    <p>Hello,</p><p> </p><p>Is it possible to have an intersection in a drill through reportfor a particular level which would not include its descendents?Like for example:</p><p>Dimension: Products</p><p>                            Coke</p><p>                            Pepsi</p><p>   I want the drill through intersection to beonly on PRODUCTS and not on Pepsi or Cola.</p><p> </p><p>Can this be done in the drill through defination?</p><p> </p><p>Thank you.</p>

    Assuming you are using EIS for the drill through, you can set up the drill through intersection for any level or at the dimension level. If you are using Analyzer for drill through, you can set up the query to only get the dimension 'Product'

  • Error when trying to run drill through in excel.

    About 2 weeks ago we upgraded our system from Essbase 654 to 931.
    Some of our users are now getting this error message on their screen when they try to run a drill through report.
    [OLAPISVR] 1051293:
    When I look in the OLAPISVR.log the below error is being written in the log when users get the above error.
    [Wed Jul 16 09:08:56 2008] /IS//0x0/1216217383/Error/1051293/Build-AIS93100B113
    EssbaseAPI: Login fails due to invalid login credentials
    [Wed Jul 16 09:08:56 2008] /IS//0x0/1216217383/Error/0/Build-AIS93100B113
    Analytic Services Error Number 1051293.Failed to Login to Analytic Services Server.
    They are able to logon to the essbase database and do a retrieve fine in Excel, but not drill through. It looks like just before they start to get this error they have changed their network password.
    We are not using shared services to administer the security. We are using an in house application for that. Also the users are set up to use external authentication.
    We did not encounter this error with the 654 version.
    Since the users ids are not changing I assumed the problem is with their password.
    Anybody have any thoughts on what has to be done to fix this error?

    Within EIS, you might have to test all of your Drill-Through reports again for connectivity.
    I believe Excel Drill-through is closer to the LRO (Linked Reporting Objects) functionality.
    The real reports are created and managed with in the EIS application as "Drill Through Report"
    These reports also have a special process for refreshing their data.
    Brian Chow

  • Hyperion Planning Drill through

    Hello All,
    Please suggest Essbase Studio if works for the below scenario of our environment.
    We have a Planning cube and Drill through defined in planning cube using EIS in the planning cube. We want to use Essbase studio 11.2.1. instead of EIS and define drill through on the same planning cube.
    I did some research on Essbase studio and did not find a way to just specify drill through on planning cube without building the outline from Studio. Can any one suggest if it is possible to define drill through on planning cube from studio or we have to stay with EIS with the current architecture.
    Thanks and appreciate your response.

    As far as I am aware there is no direct integration so the outline still needs to be built from studio.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • SQL Drill Error

    We are in the process of upgrading from 5.0.2 p11 to 6.5.1. After uninstalling 5.0.2 p11 from user desktop and installing 6.5.1 I get the following message everytime I open the excel add-in: "Could not load SQL drill-through customadd-in". Tech support said to remove the entries in the Essbase.ini file. The problem with that is that is NOT a Essbase.ini file on the PC. Any help would be appreciated.ThanksMike

    Don't work with Essbase release 6.5.1 since the essbase.ini file is not used anymore (cf. registry)But, it is because of the "sqldrinl.dll" which is missing in the essbase\bin repertory.I've tried this by copying the "sqldrinl.dll" file from an old release 5 version of Essbase to the 6.5.1's and it's fixed the problem.Nevertheless, I can't trust in this kind of solution.

  • Enable/Disable Drill-Through Reporting?

    Hi,
    We have a BSO app which has Drill-through reports (defined in EIS).
    Reports are working fine.
    Is there a way to disable/enable drill-through reporting on an App/DB using MAXL?
    Appreciate your thoughts.
    Thanks,
    Ethan.

    Glenn,
    Thank You for the response.
    I am not exactly able to understand how this whole drill-through reporting concept works technically.
    We define meta-outlines in EIS. Define Drill-through reports for Meta-outlines.
    We build the cubes in Essbase using the EIS Meta-outlines.
    Drill-through reports are available for these cubes from excel Add-in.
    I am clear till now, now starts my confusion...........
    I assume there will be a connection to EIS whenever user does a drill-through through Excel Add-in.
    When I rename the Application in Essbase, I see drill-through reports are still available.
    Are there any files/artifacts (like filters or scripts) on the Essbase app that correspond to drill-through reports?
    Is there a way to tell if the app is created using EIS or not, just by looking at the app in EAS?
    I believe I am asking the complete concept :).
    Appreciate your response.
    Thanks,
    Ethan.

  • To enable drill through in EISeveryleaf membe of dimensionis at samelevel

    Hi All,
    I a facing a drill through problem in EIS,to enable drill through feature in EIS,every leaf member of a dimension must be at same generation,is it correct?
    Plz guide me in this as it is very urgent.
    Thanks,
    Ravi

    This link will explain the difference between a Balanced, Unbalanced, and ragged hiearchy. It should help you to understand better.
    http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.db2_olap.doc/cmdhierarchy.htm
    Hybrid Analysis requires hierarchy is balanced, relational drill thru does not.
    Are you planning to use Hybrid Analysis? If not, don't worry about balanced hierarchy.

  • 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]

  • 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

Maybe you are looking for