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.

Similar Messages

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 with parameters that user can change

Hi Team,
Need to provide user the ability to select the parameters in drill through report.
But even after changing parameters to different values and click view reports.Its getting reset to the parameter that being passed from main report.
Is there any way we can override these parameter values in drill through reports so that It can also work as normal report.
Thanks!

The user is interfacing with the main report so add the needed subreport parameters to both reports. In the main report, select the subreport > properties > Parameters. add the subreport parameters and set the value to the same parameter in the main
report by clicking expression builder (fx) and selecting the appropriate parameter.
"You will find a fortune, though it will not be the one you seek." -
Blind Seer, O Brother Where Art Thou
Please Mark posts as answers or helpful so that others may find the fortune they seek.

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

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.

Can't access drill through report from add-in

I've created a drill through report via Essbase Studio. I tested it within the Studio application and then associated it with a model. To be extra sure, I even deployed the members to the outline and reloaded data to the cube. However, when I double click a data cell in the Excel add-in, I do not see the linked object drill through report. I've made sure the linked objects check box is marked under options (in the add-in). I've got full Essbase rights to the cube and I am a cpAdmin in Studio (though I even added cpViewer, just to be sure). Anything I could be doing wrong, or is there a setting I'm missing somewhere?
I appreciate any help.
Thanks,
Matt

Yeah, its an older version of the add-in, 7.1.2. I've poked support to see if it is possible to drill through from that version to a drill through report created in Studio 11.1.1.3--my client has quite a few users using older versions of excel due to legacy apps. They will have smart view installed, but its not up and running yet, so I can't test it with that.
Thanks,
Matt

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

Problem with EIS drill through reporting

Hello, Please help me with this. We are using Drill Through reports with EIS 7.1 and Essbase 7.1 in AIX environment. (These are the IBMDB2 Olap versions, not directly from Hyperion.) For some reports when retrieved on a member with more number of children, the Integration server gets killed and we get the following error ESSDTU {ESSNET MESSAGE} Network error [10054]: Cannot Send Data Following is the information in the server log file: [Thu Jul 13 4:39:04 PM 2006] /IS/Listener/0/Informational/1051001/Build-EIS71B168 Received client request Login [Thu Jul 13 4:39:04 PM 2006] /IS/Coordinator/0/Informational/0/Build-EIS71B168 Executed client request 'Login' in 0 seconds [Thu Jul 13 4:39:04 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Initialization completed, 'Worker' service is online. [Thu Jul 13 4:39:04 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Received client request Get Drill-Through report [Thu Jul 13 4:39:04 PM 2006] /IS//0x0/1152826749/Informational/0/Build-EIS71B168 Successfully loaded the OLAP Model 'OM1' [Thu Jul 13 4:39:05 PM 2006] /IS//0x0/0/Informational/1051034/Build-EIS71B168 EssbaseAPI: Logging in user [User1] [Thu Jul 13 4:39:05 PM 2006] /IS//0x0/0/Informational/1051035/Build-EIS71B168 EssbaseAPI: Last login on Thursday, July 13, 2006 4:24:33 PM [Thu Jul 13 4:39:06 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Executed client request 'Get Drill-Through report' in 2 seconds [Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Received client request Get Drill-Through report attributes [Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Executed client request 'Get Drill-Through report attributes' in 0 seconds [Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Received client request Get Drill-Through report data [Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Drill Through Report for Essbase Server:Server1.corp.com Application<img src="i/expressions/face-icon-small-happy.gif" border="0">T1 DB<img src="i/expressions/face-icon-small-happy.gif" border="0">B1 User:User1 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Unknown flag [JDBC DSN] found, ignoring it/Build-EIS71B168 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Found Q command line parameter and a value of 128 is set to it/Build-EIS71B168 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Setting configuration variable, server home, to 'c:\ibm\db2olap\is'/Build-EIS71B168 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Setting configuration variable, temporary directory, to 'C:\DOCUME~1\malkar\LOCALS~1\Temp'/Build-EIS71B168 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Setting configuration variable, log file name, to 'c:\ibm\db2olap\is\log\olapisvr.log'/Build-EIS71B168 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Setting configuration variable, Essbase message database, to 'C:\ibm\db2olap\bin\essbase.mdb'/Build-EIS71B168 [Thu Jul 13 16:39:17 2006] /IS/Coordinator/0/Critical/2002003/Build-EIS71B168 Invalid session identifier, please log in to Essbase Integration Services Server again. [Thu Jul 13 16:39:28 2006] /IS/Coordinator/0/Critical/2002003/Build-EIS71B168 Invalid session identifier, please log in to Essbase Integration Services Server again. Please let me know if this is something to do with the EIS limitations or some setting Thanks Kris

Normally if the drill through report fetches a wrong combination of members or huge amount of members than the way it was designed in the Drill through Report template. The database may fail due to improper query. Check the database and table status. Also fetch the report with proper combination of members.

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

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 with Downloaded Excel Drill Through Report

Hello! Please help!
I am having problem with the excel downloaded drill through report. Downloading the report is ok, but when I open the downloaded report, it always have this error:
View Display Error
Error generating view. Error getting cursor in GenerateHead
Error Details
Error Codes: OAMP2OPY:EHWH2A7E
A numeric value was expected (received "0").
The parent report is ok. No such error is being encountered whenever I tried to open downloaded parent report.
I am using OBIEE 10.1.3.4.1 version.
Regards,
MJ
Edited by: user13803157 on Oct 12, 2011 7:34 PM
Edited by: user13803157 on Oct 12, 2011 7:34 PM

This is a known bug. Here are the Metalink details:
Cause
This is due to bug 8394579 - Numeric Input Results in Non-Numeric Error.
Solution
Download and apply patch 9492821. This includes a fix for bug 8394579, even though it is not listed in the readme as being included.
Note that the patch is password protected. Contact Oracle Support for a password.
An alternative solution is to upgrade to OBIEE 11g.
If this was helpful, please mark the response as correct.

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

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

Building Drill through reports from aso cube using odi in webanalysis11.1.3

I need some urgent help as i have a important requirement for an essbase aso cube .I was trying to establish a database connection to build a drill through report in webanalysis from oracle datawarehouse.the integration tool which we are using to get data from oracle datawarehouse to hyperion is odi.My question are
1) Can drill through reports be built using odi like eis from an aso cube?if yes whats the procedure?
2) is there any alternate ways to bring transaction level or relational data for reporting in webanalysis?
regards,
praveen.
Edited by: user13070887 on Oct 11, 2010 3:48 PM

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

Drill Through Report With Essbase Studio

Similar Messages

Maybe you are looking for