SQL statement in Drill-Through

Hi, when you make a drill-through in excel add-in, is some way to get sql statement in excel? without open the EIS console.
I need this because Drill-through don't work well in a metaoutline with filter IN, so the user can use the query to execute the sql statement directly in the database.

there is no functionality to get the SQL that is about to be executed in Excel. There is a way to edit the columns or add filtering, but you really don't get the SQL statement.
You would have to design it yourself. You could grab the sql statement that is generated in the metaoutline and bring it into excel and have a macro that does the replacements.

Similar Messages

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

  • Studio Drill-Through Works in Excel Add-In but not Smart View

    So I have a drill-through defined that works fine in the Excel Add-In. But, when I try to drill on the same intersection in Smart View, I get "No drill-through reports found at this location." I used the same member combinations for both, so I know the intersection is correct. Am I missing something simple?
    -Brian

    There are some limitations on drill through:
    These are two ports >>transport.port and server.httpPort.used to communicate with Essbase Spreadsheet Add-in and Hyperion Smart View.
    In Hyperion Smart View, drill-through will not work properly. You must refresh the port number stored in the cube by following the instructions in "Updating Cube Linkage" See the Essbase Studio Online Help or Essbase Studio User's Guide.
    Change the HTTP Port Number:
    If you add an entry for the server.httpPort property in the server.properties file to change it from the default setting of 9080, the following is the state of drill-through connectivity on cubes built prior to the port adjustment.
    Note: Cubes built after the port adjustment will work properly. In Smart View, drill-through will work properly.
    PS:
    With shared connections, Smart View always connects first with the EPM Workspace Web application to authenticate the user and then connects to each provider using the EPM SSO token. With private connections, SmartView authenticates with the provider
    Adding to solution if your using 11.1.1.3.01 try adding PATCH:9779433 will help
    Edited by: KVC on Nov 9, 2011 1:38 PM
    Edited by: KVC on Nov 9, 2011 4:29 PM

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

  • 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

  • FDM drill-through to source data residing in SQL Server

    Hi-
    I am trying to create an FDM app allowing for drill through down to the source residing in SQL Server tables. Is it currently possible with a custom integration script which pulls data from the source and some out of the box functionality which traces back to the source data? The drill through stops at FDM work table but I need to be able to see live data in the source. What do I need to do or install to achieve that? Thank you in advance.

    Well thats news to me. I know there are some custom solutions offered by partners which can drill back to any ODBC source but I've not seen a Oracle offering. Marketing literature is not always the most reliable source of information :)

  • How to call a FoxPro .prg file through SQL statement

    I created a program exclusive.prg which basically consisted of the statement USE my table exclusive. How can i call this function through a SQL statement using java

    Hi,
    Thank you for he reply.
    Runtime.getRuntime().exec(..)works fine with .exe files.
    but, when a foxpro program file(.prg) is compiled, a (.fxp) file is produced and not a .exe file
    when i write some thing like
    statement.execute("exclusive.fxp")i'm getting an error. here is the stack trace
    java.sql.SQLException: [Microsoft][ODBC Visual FoxPro Driver]Syntax error or access violation
         at sun.jdbc.odbc.JdbcOdbc.createSQLException(Unknown Source)
         at sun.jdbc.odbc.JdbcOdbc.standardError(Unknown Source)
         at sun.jdbc.odbc.JdbcOdbc.SQLExecDirect(Unknown Source)
         at sun.jdbc.odbc.JdbcOdbcStatement.execute(Unknown Source)
         at excel.TestMom.main(TestMom.java:28)i also tried using
    statement.execute("do exclusive.fxp") and
    statement.execute("do exclusive.prg")I got the same error.
    Dont know what else to do.Can you please suggest some way to work around.

  • 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 statements through web based decelopment approach

    Hi,
    I am using the web based development workbench. I wish to create, insert and select tables using SQL statements only and not through HDBD language. Please let me know how it is possible. as of now, i see a tutorial which makes use of the HDBD language constructs only.
    Thanks,
    Murali.

    Hi Murali,
    I assume you are using a HANA Trial instance on HANA Cloud Platform. Also I assume that you already managed the web-base development workbench there.
    If you are in the workbench, you can open the catalog view like this (Check for the "plus" symbol in the upper left corner):
    In the catalog view, then check the "SQL" Button, again in the upper left corner:
    You now have a shell to execute SQL directly.
    Please consider: If you are using a HANA Trial instance, certain queries might not work because of missing permissions.
    Best,
    Thomas.

  • 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

  • Iterating through the result of a multiple row sql statement

    Hi all,
    I would like to access the results of a multiple row sql-statement. However I can't find out how to do this, can you help me here?
    I have tried using the "node-set" functions in xpath, but I can't seem to get it right.
    How should I approach this scenario?
    Sincerely
    Kim

    The jdbc service has the option of returning xml back to you ...if you do it this way then you can interogate the xml

  • RSRV? Drilling through Report times out sometimes

    Hi,
    I have reviewed several documents on RSRV on SDN but I have some specific questions.
    1.  While drilling down on a particular report, sometimes it would timeout. Can you direct me how to use RSRV to figure out the problem and fix?
    2.  Also, I saw a caution in one of the postings to be careful running RSRV on production. Does RSRV automatically begins the repairs or you get the chance after the diagnoses to make a decision to repair or not?  What really can go wrong during the repairs?
    3. Also, I know RSRV has these options:
       a. Master Data Consistency Checks
       b. Transaction Data Consistency Checks
       c. Size of Dimension tables
       d. Checking SID values
       e. PSA duplicate record check
       f.  Checking Aggregates
       g. Partitions of Info cubes etc...
    Which of these options really will help me identify the intermittent problem I am having with the report? I will appreciate some stepwise guidelines on how to step through to figure out the problem.
    Thanks

    Hi,
    I tried RSRT; entered Query name; Query Display: List   
    Parameter 1 or 2  (I chose 1)
    I then selected:
    Display run schedule
    Do not use cache
    Do not suppress messages/warning
    The selection screen of the report came up report and I completed it. After execute+Debug I get the data below.
    What do I do from this point to figure out the problem and fix it:
    SQL Statement                                                                               
    SELECT                                                                               
    /*+                                                                               
    STAR_TRANSFORMATION  FACT(F)                                                                    
    "DT"."SID_0CALMONTH" AS "S____022" ,"D5"."SID_0DOC_TYPE" AS "S____130" ,                        
      "DU"."SID_0CURRENCY" AS "S____023" ,"S1"."MATL_GRP_4" AS "K____404" ,                           
      SUM (  "F"."G_AVV010"  )  AS "Z____084" , SUM (  "F"."G_AVV140"  )  AS "Z____093" ,             
      SUM (  "F"."G_AVV150"  )  AS "Z____223" , COUNT( * )  AS "Z____030"                             
    FROM                                                                               
    "/BIC/FATRUMMNP" "F" JOIN "/BIC/DATRUMMNP3" "D3" ON  "F" . "KEY_ATRUMMNP3" = "D3" . "DIMID" JO
      N "/BI0/SMATL_GRP_4" "S1" ON  "D3" . "SID_0MATL_GRP_4" = "S1" . "SID" JOIN "/BIC/DATRUMMNPP" "DP
    Execution Plan                                                                               
    SELECT STATEMENT ( Estimated Costs = 42 , Estimated #Rows = 1 ) 
         5  30 HASH GROUP BY                                         
               ( Estim. Costs = 42 , Estim. #Rows = 1 )              
               Estim. CPU-Costs = 15,234,394 Estim. IO-Costs = 34                                                                               
    5  29 HASH JOIN                                         
                   ( Estim. Costs = 41 , Estim. #Rows = 1 )          
                   Estim. CPU-Costs = 13,191,632 Estim. IO-Costs = 34
                   Access Predicates Filter Predicates               
    5  12 PARTITION RANGE SINGLE                               
           ( Estim. Costs = 5 , Estim. #Rows = 0 )              
           Pstart: KEY Pstop: KEY                               
           Estim. CPU-Costs = 19,122 Estim. IO-Costs = 4        
         5  11 TABLE ACCESS BY LOCAL INDEX ROWID /BIC/FATRUMMNP
               ( Estim. Costs = 5 , Estim. #Rows = 0 )          
               Pstart: KEY Pstop: KEY                           
               Estim. CPU-Costs = 19,122 Estim. IO-Costs = 4    
             5  10 BITMAP CONVERSION TO ROWIDS                                                                               
    5  9 BITMAP AND                                                                               
    5  4 BITMAP MERGE                                                                               
    5  3 BITMAP KEY ITERATION              
    Thanks

  • 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."

Maybe you are looking for