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.

Similar Messages

Enabling Drill Through causing Essbase Integration Server hang.

During the automation process using olapicmd command and *.cbs we are enabling Drill Through which is causing Essbase Integration Server hang.
We don't get any error message in log file. Plus sometime its run successful , also when we run this manually going to EIS console, it run fine.
Thanks in advance
-Piyush

Hi Kishore,
Thanks for your prompt reply......
I have checked in before itself the Drill down option ......
I am not able to understand whats the issue we are able to drill through in EIS till last level but after improting in OBIEE we are not able to drill through to last level, in the last level it showing no results....
I am not able to find the solution any other suggestions ?
Regards,
Tarang Jain

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

Enabling drill through using FR

Hi Team ,
We have configured Drill through in FDMEE and we are able to drill from web-forms and smart view to FDMEE . Please advise if we can drill to FDMEE from Hyperion reports also .
Basically if i can drill through from web-forms for an intersection how can i enable drill from the same intersection from HFR .
Regards,
Roshin Rasheed

It is possible .. Check below link for detailed explanation of how to enable that : http://www.oracle.com/technetwork/middleware/financial-management/tutorials/obe-fr-erpidrillthru-100179.html
Cheers !

Enable drill through feature in a Financial Reporting Report

Hi,
my Hyperion system version is 9.3.1. I need to realize some Financial Reporting reports using the Drill Through feature but i don't know how activate this feature.
Anybody can hel me?
Thanks in advance.
Stefano

One way is related content, which drills to another report based on the intersection clicked on by the user:
Check out the fr user guide (chapter 7) for more info:
http://download.oracle.com/docs/cd/E10530_01/doc/nav/portal_4.htm
For setting up drill-through, you need to define the Hybrid Analysis relational source in Integration Services Console, check out the Hyperion Essbase – System 9 Database Administrator's Guide from the following link:
http://download.oracle.com/docs/cd/E10530_01/doc/nav/portal_3.htm
Regards, Iain

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.

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)

Drill-Through from Roll-up member

We have drill through enabled for base level members, but can anyone provide an example of a drill-through query that works when originated from either a roll-up member or base level? Thank you.

Hi Boon,
One thing you could try doing is adding an OR clause to your Drill Through query that queries the member table
This is the sample query from ApShell:
SELECT tblSalary.Name, tblSalary.PayDate, tblSalary.NetPay, tblSalary.GrossPay, tblSalary.Dept FROM DrillTest.dbo.tblSalary tblSalary WHERE (tblSalary.Dept='%ENTITY%') ORDER BY tblSalary.Name
To query for parent entity members also it would look like:
SELECT tblSalary.Name, tblSalary.PayDate, tblSalary.NetPay, tblSalary.GrossPay, tblSalary.Dept FROM DrillTest.dbo.tblSalary tblSalary WHERE (tblSalary.Dept='%ENTITY%') OR (tblSalary.Dept IN (SELECT ID FROM ApShell.dbo.mbrEntity WHERE PARENTH1='%ENTITY%')) ORDER BY tblSalary.Name
The statement after the "OR" looks at the parent member column (PARENTH1) of the dimension table (mbrEntity) but returns the ID column (i.e. the children of those parent members).
HTH,
John

How Enabling ERP Integrator Drill Through from a Grid

Hi All,
Can any one tell me how to see the source data by using FR.
some where i saw we can see this by using Enabling ERP Integrator Drill Through from a Grid.
but i dont know how to set this...
can any one help on this...

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 Enable Drill Down in WebI through Infoview

Hello Experts,
I have WebI report, I am running through Infoview and I see drill down option is disabled, can anybody help me how to enable drill down option.
Thank you
Ravi

HI Ravi,
Log on to CMC -> Application -> Right Click on Web Intelligence Rich Client -> Select your user -> Assign Security -> Advanced tab -> Select "Unassigned Rights" in Common Filter Settings -> Select Enable Drill Mode in Rights Name Column -> And assigned grant level to it.
Hope this help.
Regards,
Rishit

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

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

BPC 7.5NW Drill-through to FIM

Hi all,
I upload data to BPC 7.5 NW SP06 through FIM. I tried to set up the Drill-through functionality of BPC so as to see the analysis of the trial balance uploaded in FIM, but with no success. The How-to-paper for drill-through functionality for NW, uses drill-through only to BEx and ECC, not FIM. In SAP help for BPC NW, there is an example for FIM but it is too general.Has anyone faced the same situation? Or any idea?
Thanks
Regards,
Maria

Hi,
I am trying DT to ECC funcationality in BPC 7.5 NW version. I am trying to TD from a P&L report based on hierarchies.
I would like to know how people are using drill-through on parent level nodes within their BPC hierarchies.
I hear that there is something called which is a hierarchical view of their objects/metadata in ECC. How is it related to BPC drill through?
In my example, the DT is from a P&L report that consists of Functoinal Area & P_Account (with a mix of hier nodes and base members) and Company Code in Colum (in summarized columns like N. America, Europe, etc). The current View migth have profiit center hier nodes that comprise of multiple base member profit centers.
We would like to to drill thorugh from a cell that is an intersection of FuncArea-Account parent node and Comoamy Code parent node (N. America) to an ECC profict center transaction - K5EZ (Profit center line item).
Any help/guidance with some documentation if possible is appreciated.
Thanks in advance.
Regards
Raj

Getting error while drill through a report

Hi,
I am getting this following error when I drill through a report and the OFA application freezes. I hope this is problem with the OFA installation.
(MXMSERR) S does not exist in any attached database.
What does it mean and what could be the problem ?
Please let me know how to rectify the problem?
Thanks
Murugesan

Hi,
If it's not the universe limits, then I think you've hit the "MDX result contains too many cells" (more than 1million) problem.
So, I suspect a long running query, no filters/variable restrictions, and You've probably got a dump in ST22.
I don't know what BW you have, but if it is BW 7, do you have Enhancement Pack 01 and SP05<->10 ?
You should check out all the latest corrections from component BW-BEX-OT-MDX
the final proof of the pudding would be to enable MDA / SOFA log , capture the MDX SELECT statement and test it in BW MDXTEST - i bet you get the same error there.
regards,
H

Workaround for HFM Drill-Through when using custom dimensions ( 4) in FDM

Hi all,
we have the following scenario:
- Target Custom 3 is defined as a combination of Target Product and Target Cost Center
- Target Product needs to be obtained by mapping field "PRODUCT" in the source file
- Target Cost Center needs to be obtained by mapping field "CC" in the source file
So,
One approach would be to enable Custom5 and Custom 6 dimensions in FDM, and configure sequence so these two dims are mapped before custom 3 which has a conditional map to get
values from target c4 and c5 (using varvalues...)
The issue here is that drill-through does not work as the sql query for the intersection is looking for UD5x and UD6X as NULL, N, or [NONE], and these two columns have a value as they were mapped.
Trying to solve this issue, we configured C5 and C6 as lookup dimensions so we could create the mapping tables for them although in order to import data from source file fields we used attr2 and attr3. Besides UD5 and UD6, as expected, were not displayed in the Import and Validate/Export grids
Then the idea was to update the work table with attr2->ud5 and attr3->ud6 in a event script (importaction or befprocmap..) so ud5 and ud6 are mapped.
The problem is that we noticed that ud5 and ud6 are not updated from attributes. It seems that as they are configured as lookup dims, values may be mapped but not copied from work table to tdataseg.
If this would work, then after custom3 is mapped we could set ud5x and ud6x to [none] in order the drill-through query to work.
Having all in custom 3 dim and use mappings on combinations is not desired by the customer as they want to keep product and cc mappings separately.
I was thinking to use a dummy location for product and cost center mappings and then emulate mappings using SQL but would like to avoid this.
Any other suggestion?
Thanks!

The criteria for mapping C3 is:
- If Plan = 6 Then Target C3 = SUBACCOUNT
- If Plan <> 6 AND Account IN range [70000,70999] Then Target C3 = Target CC
- If Plan <> 6 AND Account NOT IN range [70000,70999] Then Target C3 = Target CC_Target Product
Fields in the file
- PLAN
- ACCOUNT
- SUBACCOUNT
- Source CC
- Source Product
So current solution actually is to put that logic in the import format so:
- If Plan = 6 Then Source C3 = SUBACCOUNT
- If Plan <> 6 AND Account IN range [70000,70999] Then Source C3 = "RULE2"
- If Plan <> 6 AND Account NOT IN range [70000,70999] Then Source C3 = "RULE3"
In the mapping of C3, we managed a simple script mapping checking the source C3
If source c3 = RULE 2 -> Target C3 = Target CC
If source C3 = RULE 3 -> Target C3 = Target CC_Target Product
Else Target C3 = source C3 (which is SUBACCOUNT)
C5 (Cost Center) and C6 (Product) are mapped before C3.
In order to make Drill-Through working, we save UD5X and UD6X in ATTR2, ATTR3 so the user can see it, and we set then UD5X and UD6X to [None] so the Drill_Through SQL Query returns the values from FDM. If after loading the user goes to validate step, he will see [None] in C5 and C6 but actually this does not really matter as C3 has already been mapped and is the value to be loaded. If the want to review target product or target cc then they drill down to attribute information.
regards

To enable drill through in EISeveryleaf membe of dimensionis at samelevel

Similar Messages

Maybe you are looking for