Essbase Studio Drill-Through Report

Is it possible to run an Essbase Studio drill-through report in a SmartView spreadsheet that is connected to a cube that was not deployed by Essbase Studio? If so, how do you associate the drill-through report with the cube?

You have to trick Studio into thinking the cube was built from Studio. In my session on Advanced Studio Tips and Tricks at the KScope conference at the end of June I detail a couple of ways to do this. It is too detailed to put into a post here

Similar Messages

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

Essbase Studio Drill-through for Recursive Hierarchy - Generation 1

I'm using Essbase Studio 11.1.2.3 to build an ASO cube. All my hierarchies are recursive (parent-child). I would like to define a drill-through report and I understand that I have to use the Advanced Settings option to specify my intersections. Now one of my dimensions is optional for the users - they don't have to specify a member (they can leave it at the highest level - dimension name on the spreadsheet). Under 'Advanced Settings' for DT report in Studio I have to specify a Generation value of 2 or greater than 2. How do I enable drill through in cells where one of the dimension is at Gen1 ? Specifying the level number didn't work. I think if you specify Level in 'Advanced Settings', drill through is allowed only if that specified level of the dimension is chosen, if Gen 2 is specified, then drill through is allowed as long as the dimension-members specified are at or above Gen2. But what about Gen1?

Yep, this is a limitation. I suggest you create two reports one that takes your "optional" dimension out and a second one that has it in. if they don't need the dimension, select the first report and if they need the filter then the second. I m always a little leery with recursive hierarchies and Gen 2 or 3 sine they create a list of level 0 members under the selection in the query and there are limits to the number of members in an in clause and at high levels in the hierarchy it is easy to surpass it (In Oracle it is 1000 members)

Essbase Studio & Drill-through

Hello All,
Can I still create a drill-through report in Essbase Studio & update a previously built [by EPMA] Essbase cube? Please consider this urgent...
Thanks,
Cheryl

Cheryl,
One of the draw backs right now of using EPMA to load Essbase cubes is that any changes that are made to your Essbase cube in EAS, etc. post a EPMA Essbase Cube deployment will be overwritten and vice-versa. EPMA is best for working with HFM and Planning right now and is not best suited for Essbase deployment right now even though it can handle simple Essbase cube deployment. If you cannot do what you need with EPMA alone then you will need to deploy using Essbase Studio, EIS, or EAS.
However, other options would be to utilize partitioning or something similar to get the drill-through capability from another "Reporting" cube. That would be the immediate solution I believe.
http://www.artofbi.com
Edited by: Christian Screen on Nov 17, 2009 9:10 AM
Edited by: Christian Screen on Nov 25, 2009 12:30 PM

EPMA Essbase Studio Drill-through

If I deploy a Planning application via EPMA is it possible to configure drill-through from Planning via Essbase Studio?
Thanks,
Jz

The drill-through path from Planning is from a web-form to FDM.
Can this hack drill through from a Planning web-form or would I need to created reports in Planning to drill-through?
The Studio documentation only talks about Reports...
Thanks,
Jz

Issue with Drill Through Reports in Essbase Studio.

Hi,
we are using essbase studio to drill through to the source table in Oracle.In drill through definition the query is like , select * from source where (Project IN ($$PROJECTS-VALUE$$)). Project column is located in source table and PROJECTS-VALUES are located in Essbase under project dimension and we will select the values in smart view. we are using smart view to check drill through reports.In smart view, If i select one member at gen-2 level which contains 1450 level-0 members,It is saying as error in executing the report in line 1972. Is there any limitation with IN condition , such that oracle takes only limited values like count of 999.we are facing issue only at gen-2 of project and it is working good from gen-3.
Please let me know is there any kind of certain limitation.

It is possible you are overloading the parser. If the projects table/view is a recursive join, when Studio creates the $$Project-value$$ is actaully returns all the level zero members under the member selected(at least in 11.1.2.X. If the list is huge, it might have problems. I would open an SR to see if there is a limit. It might be number of characters or values

Drill through report - Essbase Studio

Hi,
Need some help on drill through reports.
I have created a drill through report in essbase studio. I am able to drill down to the source table in SmartView. But the problem is, when I drill, it is showing me all the records in the table instead of showing me the records only for the intersection that I am drilling.
Regards,
Ragav.

You have to trick Studio into thinking the cube was built from Studio. In my session on Advanced Studio Tips and Tricks at the KScope conference at the end of June I detail a couple of ways to do this. It is too detailed to put into a post here

Drill Through Report With Essbase Studio

I have built a new minischema, cube / essbase model, and deployed to Essbase using Hyperion Studio 11.1.2.1. I created a drill-though report and was able to use the "test" feature to verify that the report returned data. The drill-through report type is relational and the association has been mode to my new cube. Restarted and confirmed the studio services were running correctly on the Essbase server. I have tried to drill-though using SmartView and AddIn, but recieve the message "No Drill Through Report at this Location". Cell styles are enabled and its not picking up my drill-through styles.
Pray tell what I should consider as my next move to troubleshoot?

Did not have the proper APS server connection selected during my testing. :D Once I connected SmartView to the proper APS server the application translated the drill-through report correctly.

Enabling drill through from Essbase cube to drill through report

The requirement is that I keep summary level information in the Essbase cube and detailed granular information (order level) in a relational table.I would like to enable drill through between the cube and the report.
Please advise what would be the best approach considering the current system architecture that is outlined below.( Hyperion suite 11.1.2.1).
Would also like to know drill thru vs hybrid analysis options.
1) ASO/BSO cube is populated through Oracle Data Integrator
2) The relational transactional table is also poulated through ODI.
3) The cube would hold summary level info while thr drill through report should provide the order level details in the same context as chosen in the cube.
Would appreciate guidance on the best way forward.
Thanks & Regards,
Anirban

Incidentally we had been trying to use Essbase studio as an option.But there are 2 oints that we are trying to investigate.
1) Can we bypass deployment of data and metadata everytime through Essbase studio after the initial outline is delpoyed? In the system architecture the relational tables are populated using ODI. We would like to load the data and metadata through ODI into the cube. Eeven then can we implement drill thru bypassing deployment through Essbase Studio?
2) If Essbase studio is imperative for drill through then what are the batch automation options for deployment through Essbase studio? Ideally the option should be after the relational tables are populated through ODI then the Essbase deployment should be invoked and batch script should load the data and metadata through Essbase Studio.
Please advise.
Thanks,
Anirban

How to increase number of rows displayed in Essbase drill-through report?

Hi
By default, the maximum number of rows per Essbase drill-through report (via Integration Services) is set to 1000. Could anyone tell me how to change this limit please?
Regards
Chandra

Is this for an EIS drill through report that drills through to get RDBMS data, using spreadsheet add-in for example? If so check and see if "Maximum rows per query" in EIS is currently set at 1000 and try to increase it. (I don't recall hitting a 1000 limit in the past, perhaps your report is set at that? or if this is through Web Analysis maybe WA is governing it)
To set/change a query governor in EIS:
1     In the Drill-Through Reports dialog box, select a report name.
2     Click Edit to open the Report properties dialog box.
3     In the Report properties dialog box, select the Governors tab.
4     In the Maximum time per query (in seconds) text box, enter the maximum query time.
For example, to stop a query that takes longer than 100 seconds, type 100.
5     In the Maximum rows per query text box, enter the maximum number of rows to retrieve.
For example, to stop a query that retrieves more than 200 rows, type 200.
6     Click OK.

Error in Drill through reports

Hi All,
I need a help with Drill through reports in Essbase Studio.
I created a drill through report successfully. Now When I trill to access that report using SmartView, I am able to see the report at generation 2, but as soon as drill down, i am getting following error.
" BPM drill through functionality not available. EMC required in MDX query "
Please advice.

Can anyone please give some suggestions ? I guess I figured out that whenever there is a duplicate member present in a hierarchy, its gives me the following error:
*" BPM drill through functionality not available. EMC required in MDX query "*
Please advice.

Drill through report

Hi Friends,
I am new to this blog. I have a quick question using drill through report. I have deployed BSO cube using EAS / rules files. I want to create a drill through report. I know how to create a drill through using essbase studio but not from EAS. Please advice.
Thanks
Andy

It will be available to the participants of the conference. (it is already posted, but I have changes to upload). I'm not sure when ODTUG will make presetations generally availalbe. IT is not typically for a number of months. Also although the presentaion sildes have information, there is a lot of verbage to go along with it. I'm sure it will end up as an interRel webcast later in the year, but I would not know when. I'm sure none of this helps you. but it is a bigger topic than applicable to the forum

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

Drill Through reports takes too long

Hi all,
I need some suggestions/help with our drill through reports. We are using Hyperion 11.1.1.3 and the cube is ASO.
We have drill through reports set up in Essbase studio for drilling down from Essbase to Oracle database. It takes too long (like 30 mins for fetching 1000 records) and the query is simple.
What are the changes that we can do to bring down this time. Please advice.
Thanks.

Hi Glenn,
We tried optimizing the drill through SQL query but actually when we run the directly in TOAD it takes *23 secs* but when we do drill through on the same intersection
it took more than 25 mins. Following is our query structure :
(SELECT *
FROM "Table A" cp_594
INNER JOIN "Table B" cp_595 ON (cp_594.key = cp_595.key)
WHERE (Upper(cp_595.*"Dim1"*) in (select Upper(CHILD) from (SELECT * FROM DIM_TABLE_1 where CUBE = 'ALL') WHERE CONNECT_BY_ISLEAF = 1 START WITH PARENT = $$Dim1$$ CONNECT BY PRIOR CHILD = PARENT UNION ALL select Upper(CHILD) from DIM_TABLE_1 where CUBE = 'ALL' AND REPLACE('GL_'||CHILD, 'GL_IC_', 'IC_') = $$Dim1$$))
And ----same for 5 more dimensions
Can you suggest some improvement ? Please advice.
Thanks

Essbase Studio Drill-Through Report

Similar Messages

Maybe you are looking for