Drill Through report Intersection levels

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

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'

Similar Messages

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

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 reports in EIS 7.1.X

Hi, 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.

Hi, I am also facing few issues related to AIS: I am unable to use Drill Through (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 (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 Can anybody help me?

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

Passing different (multi-) values for parameters to drill-through report, based on clicked subtotal in main report

In Report Builder 3.0, I have made a main report in which the user can filter the underlying dataset using three parameters (all multi-value). The report shows totals grouped by these three parameters, as well as a grand total. What I want is to click
on a total, which then opens the drill-through report for the corresponding records. I have achieved this for the grand total; the action in the corresponding text box passes all selected values of the parameters to the drill-through report.
What I cannot figure out is how to make this work right when clicking on a subtotal. When I use the same expression as for the grand total, the same values for the parameters are passed, instead of the subset that apply to the corresponding text box in the
main report. I expected this to work, because Report Builder /does/ correctly calculate the SUMs for the different levels, even though the expressions are the same.
My question is: how do I pass different drill-through (multi-) values for parameters, corresponding to the respective subtotals in the main report?
(FYI: I am using Microsoft SQL Server 2008 R2 and Report Builder 3.0 .)

Hello Katherine,
Thanks once more for your quick reply.
I was aware of the textbox action "Go to report", and how to pass parameters in general. My question concerned how to determine the scope of the passed multi-value parameters (to the values that apply to the respective group/subtotal). The article you linked
to is informative, but not a solution to my problem.
A colleague of mine came up with a pragmatic solution: instead of trying to determine the scope of the parameter values, now I "look to the left in the results table". The two screenshots below should illustrate this. (Screenshots are in Dutch. Specific information
is pixelated.)
Unfortunately, I am not able to post images. Once my account is verified, I will edit them in. For now, I hope the text speaks for itself enough.
[Screenshot: Drill-through parameters - 01: Report Builder tablix with subtotals]
[Screenshot: Drill-through parameters - 02: Textbox properties (selected in screenshot 01) - Action - Go to report]
The first screenshot shows the tablix in the Report Builder. The second screenshot shows the properties of the textbox selected in the first.
Notice that I do not pass parameters for the first two columns, but the actual values. I only pass the parameter (containing /all/ user-selected values) for the third column. In the textbox below the selected one, I pass the actual values for the first column,
and parameters for the last two. In the textbox above the selected one, I pass the actual values for all three columns.
The only (cosmetic) flaw this approach has is that in the drill-through report, the list of selected parameters might show values that do not occur in the (corresponding part of the) results, and only for those parameters for which the main report passes (all
user-selected) parameter values, and not the actual values in the results. The results are correct, though.
If there is a way to directly determine the scope of multi-value parameters for passing to a drill-through report, I would still like know. But for now, this seems to work.

Drill-Through Report automation through VBA

Hi,
I've been making macros using standard VBA functions in Excel Essbase. For this, I've been using functions defined in essxlvba.txt.
My Essbase database has linked objects which gives the transaction level data for selected cells.
If I call EssMenuVLinkedObjects function, the control gets passed the linked object window and this needs to be controlled manually. Which defeats my purpose of automation of drill-through retrieval. I'm searching for functions using which I should be able to bypass the Linked-Object window and Drill-Through window and get the desired data. This is because I've to retrieve huge amount of data and I want to eliminate any manual steps.
I've been exploring Oracle website and found that there are Visual Basic Main API Functions and I tried to explore them also but I could not find various constants and structure declaration.
Please help.
Subhash.

The VB Main API declarations (including functions, constants and structures) are in a file named esb32.bas. This will be in a subdirectory on the client named \api\include - exact location depends on your version.
I've never tried automating the execution of drill-through reports, so I'm afraid I can't help on the specifics.
Just a thought though - if you need to pull a 'huge amount of data' and want to do this without manual intervention, Essbase drill-through might not be most suitable mechanism. It sounds more suited to a relational extract / query tool.

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

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. 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. I'm using Essbase 7.1.5 with EIS 7.1.2 and Analyzer 7.2.5. Is anyone using Analyzer to successfully pull EIS drill through reports? Did you have to turn on the Grid API option? How is this feature turned on? Or, any other suggestions? TIA

Hi, I am also facing few issues related to AIS: I am unable to use Drill Through (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 (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 Can anybody help me?

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

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.

Drill through reports are not working fine in share point server

I Have a master report with four parameters and child report with two parameters
I deployed these two reports in share point server , my scenario is i am navigating from my parent report to child report using action (Drill Through Report Concept)
First i clicked on parent report it will ask select parameters , i have selected all parameter and click on apply in share point it will display the parent report content .
In parent report i have link to navigate child report . if i click the link it will redirect to child report and displays the child report content perfectly. upto this step every thing working fine now problem is comes to picture
I have back to in my child report when i click the that button it redirects from child to parent
But earlier selected parameters values are lossed and the parent report again asked for me to select parameters
Can you please explain me because we have migratiojn from ssrs report manager to share point .

Hi All,
Finally i got the solution there is small difference between SSRS Native mode and share point integrated mode
To overcome this issue explicitly we have to change our report expression code for SharePoint Integration mode before deployment. We have to change URL
Preparation code in the expression in report.
Below is the sample URL
="http://<<site url>>/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl"+"=/ssrs/INT/Report.rdl&rp:parameter1="+CStr(Parameters!parameter1.Value)+"&rp:parameter2="+CStr(Parameters!parameter2.Value)+"&rc:Parameters=True"
The only difference between our SSRS Report manager report expression and share point integrated mode report expression is
“rp:”
value prefixed with every parameter.
After fixing this code I am able to see the previously selected values in Parent report below are the screen shots

Passing multi value parameter to the Drill through report

Hi
I have two reports say Report A and Report B.
Both reports using same parameters.
I am Navigating from Report A to Report B using Jump to Report option.
Now when I pass multiple parameter to the Report B it only displays first parameter results.
In report B I have parameter multi value select to true.
I would like to know if its possible or not to pass multi value parameter in drill through report?
I would appreciate if someone can help me here.
Regards
Amit

Yes you can pass multi value parameters to a drill through report.
It works similar to multi value parameters for subreports, which is discussed in detail in this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=163803&SiteID=1
-- Robert

Drill Through report Intersection levels

Similar Messages

Maybe you are looking for