Business Intelligence

Hyperion, OBIEE, Qlikview Showing newest posts with label Brio. Show older posts Showing newest posts with label Brio. Show older posts

Sunday, June 14, 2009

Brio Cell Double Click
Hi, Sometimes there is a requirement wherein users would like to see the detailed data by simply double clicking on a data cell value of a summary report. This feature is illustrated in the snapshots below.

Let's say this is a summary report in a dashboard showing total sales value for some particular product category. Now for example if a user want to see the detailed breakup of value '250169.11' which is 3rd in the row. Here the user just need to double click on the cell and the detailed breakup report would appear as shown below(This is just a portion of the detailed report).

Today we will see how we can do this in Brio or Hyperion Interactive Reporting. Here the datasource for the summary report as well as the detailed report is same. To perform this1. Create a query as usual by making a database connection and selecting tables. The request line items should contain all the columns that may be required in the summary report as well as in the detailed report. 2. Process the query to retreive the results.

3. Insert 'New Pivot' to Create a pivot having presenting summary level report which then will be displayed in a dashboard. 4. Insert 'Table report' to create a table report and select all the columns you want to display in detailed level report. 5. Insert 'New Report' to create a detailed report and here select the columns displayed under the table we just created. In the picture below, take the columns displayed under the 'Table1'.

6. Insert 'New Dashboard' and drag the 'Pivot1' we created for the summary report to this dashboard. 7. Under the design mode, Right click the pivot and select 'Scripts'.

8. Under 'Event Trigger', you will notice an event 'Cell Double Click'. Write the code in the main

window to perform cell double click event. Please refer the sample code provided below and customise as per your object names and column names. Sample Code: SectionTable = ActiveDocument.Sections["Table1"] SectionPivot = ActiveDocument.Sections["Pivot1"] ReturnVal = 0ReturnVal = Application.Alert("Do You want to drill?", "Drill to Details?","Drill","Cancel") if (ReturnVal == 1) { SectionTable.Limits["Product Family"].SelectedValues.RemoveAll() SectionTable.Limits["Product Category"].SelectedValues.RemoveAll() SectionTable.Limits["Product Name"].SelectedValues.RemoveAll() SectionTable.Limits["Product Publisher"].SelectedValues.RemoveAll() SectionTable.Limits["Day Key"].SelectedValues.RemoveAll() for (i = 1; i <= SectionPivot.SideLabels.Count; i++) { if (SectionPivot.SideLabels[i].Name == "Product Category") {SectionTable.Limits["Product Category"].SelectedValues.Add(Pivot1.SideLabelValues[i])} if (SectionPivot.SideLabels[i].Name == "Product Name") {SectionTable.Limits["Product Name"].SelectedValues.Add(Pivot1.SideLabelValues[i])}} for (i = 1; i <= SectionPivot.TopLabels.Count; i++) { if (SectionPivot.TopLabels[i].Name == "Product Category") {SectionTable.Limits["Product Category"].SelectedValues.Add(Pivot1.TopLabelValues[i])} if (SectionPivot.TopLabels[i].Name == "Product Name") {SectionTable.Limits["Product Name"].SelectedValues.Add(Pivot1.TopLabelValues[i])}} ActiveDocument.Sections["Report4"].Recalculate() ActiveDocument.Sections["Report4"].Activate()} 9. Now check the syntax and deselect the design mode and in the dashboard, double click a cell value and you would be able to see the detailed break up of the selected value. Manohar Rana

Posted by Manohar Singh Rana 1 comments Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz Labels: Brio, Interactive Reporting Links to this post Please Rate:

Saturday, December 27, 2008

Hyperion Brio Impact Manager
Hi, Today, let's understand and discuss about the Impact Manager feature available in Brio or Hyperion Interactive reporting. Impact Manager is a utility which can be very useful in situations where you want to find out the

dependencies of a particular column of a database table being refrenced in Brio data models and queries. let's say for example there is a proposed change in table definations of some particular table and you want to identify the brio reports which are going to affect by this change. To perform this job manually by openning every single document and checking for those tables and columns used in the report is not a practical solution especially when you have thousands of reports published in Hyperion Workspace. Not only that. After identifying those reports you may want to update all the reports automatically by the system only. Another similar scenario similar to this is let's say you are going to add a new column in a particular table and you would like to see what possible reports may possibly require to use this new field. The IT may not want to individually ask all the users if they want to or intend to use this new column in their reports. To start using the Impact Manager utility, you first need to enable the Harvesting option. To enable harvesting option, log on to Hyperion Workspace using a User ID with Administrative privilages. Go to Navigate- Administer- General. This will display all the general properties. Select 'Enable Harvesting' option and save. This option is not enabled by default.

The next step is to invoke Harvesting. Now what does this invoking will do? When you invoke Harvesting, the system will read all the Brio documents published in Hyperion Workspace and then extract and store the metadata in the tables created in the database repository.

When you first invoke it, the system will create some tables (around 40) in the database repository with names starting from 'V8_H%' for the purpose of storing the metadata information. Also, once invoked this process may take several hours(around 6-7) to complete for a system having thousands of published reports. The metadata repository will have information related to Report sections, Tables and columns used in reports and Section dependencies. To invoke Harvesting, From Navigate- Impact Manager-Synchronise Metadata select 'Run Now' option and click on 'Submit'. If you want to schedule it for some other time, you can choose 'Schedule' option.

You can check the status of this invoking process by selecting Navigate-Impact Manager- Show task status.

The system will tell you the status for every published document. Some of the status may show failed due to various reasons like not finding the suitable connection information. You may need to manually go and check those documents and try to correct it.

Now once this process is complete, you would like to see how this works. There are three options1. Create an SQL query by combining the tables and selecting the appropriate columns. 2. Create a bqy document with a query similar to point number 1. 3. Using 'Impact of Change' report available with Impact Manager. To use this report, select navigate- Impact Manager- Show Impact of Change.

Now, In the picture above there are some tabs aligned Horizontally. Select the first tab 'Home'.

Simply select a table or column in the filter and click on 'Set Filter' to give you the dependencies. The tabs you see will provide information to queries, datamodels, tables and columns related to the filter you had set. Here in this slide I have selected 'RDBMS Table Name'. You can choose from options available under the drop down menu like Document name or topic name. Some of the tables which would be useful to prepare the query are: 1. V8_H_QRY_COLUMN- Holds info such as SQL definition which points to actual base table

and column with corresponding query column name. 2. V8_H_QRYCOL_DMCOL- Stores cross reference data which can be used for linking document objects and database objects. It has column id for IR document and corresponding database column id . 3. V8_H_HPSU_COLUMN- Stores column information as defined in IR documents and linked to its Table ID. 4. V8_H_HPSU_TABLE- Stores table information as used in IR documents and has a link. 5. V8_H_DOCUMENT- Stores path, parent folder, document name, version, time_harvested and document. Hope this would help. Manohar Rana Posted by Manohar Singh Rana 2 comments Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz Labels: Brio, Interactive Reporting, Workspace Links to this post Please Rate: Newer Posts Older Posts Home Subscribe to: Posts (Atom)

About Me

Manohar Singh Rana Mumbai, Maharashtra, India Our greatest glory is not in never failing, but in rising up every time we fail. This is my personal blog. The views expressed here are mine alone and not those of my employer or anyone else. View my complete profile

Topics

Administrative Services (3) Brio (2) Business Intelligence (1) Essbase 11.1.1 (5) Essbase 9.3.1 (3) Essbase Excel Add-in Demo (1) Essbase Tutorial (1) Financial reporting (3) Hyperion Reporting and Analysis Architecture (1)

Hyperion Vs OBIEE (2) Implementing Business Intelligence (1) Installing Essbase (1) Interactive Reporting (8) interview questions (3) Learn Essbase (1) Learn Qlikview (2) Magic Quadrant (1) Migration (2) My Blog (1) Open Source BI (1) Pentaho (1) Planning (3) Project Implementation Life Cycle (1) Project Management (1) Qlikview (4) Qlikview Vs Others (6) Reporting and Analysis Architecture (1) SQR Reporting (2) Visual Explorer Demo (1) Webanalysis (1) Workspace (3)

Blog Archive

2010 (1) o March (1) BI Project Implementation Life Cycle 2009 (9) o July (2) Hyperion Essbase Book Qlikview Personal Edition o June (1) Brio Cell Double Click o February (1) Essbase Application Migration o January (5) Interactive Reporting with Essbase Hyperion Financial Reporting- Row Headings Before Pentaho - Open Source BI Gartner BI Magic Quadrant 2009 Security Filter Essbase Tutorial

2008 (41) o December (9) Hyperion Workspace 11 Qlikview - Slider Hyperion Interactive Reporting Enhancements- Live ... Hyperion Interactive Reporting Enhancements - Char... Hyperion Interactive Reporting Enhancements Hyperion Brio Impact Manager Essbase Interview Questions Hyperion Visual Explorer(HVE) Demo Hyperion Essbase Demo o November (1) Implementing Business Intelligence o October (3) Oracle Hyperion EPM 11.1.1 Installation and Config... Hyperion Planning Hyperion customer move to OBIEE o September (4) Learn Hyperion Planning Hyperion Interactive Reporting Disadvantages Hyperion Essbase Interview Questions Hyperion Essbase Migration o July (16) Hyperion Planning Tutorial Hyperion WebAnalysis Tutorial Hyperion Workspace Hyperion Essbase 11.1.1 Hyperion Essbase 11 Business Intelligence Interview Questions Getting started with SQR Production Reporting Multiple pages in Hyperion Financial Reporting Magic Quadrant for Business Intelligence 2008 Hyperion Licensing Information Hyperion Reporting and Analysis Architecture Siebel Analytics (OBIEE) Vs Hyperion Essbase Learn Qlikview Whats New in Hyperion Essbase 9.3.1 Business Intelligence Will Decline Getting Started with Qlikview o June (7) Working with Hyperion Administrative services Hyperion SQR production reporting tutorial Hyperion Interactive Reporting Tutorial Install Hyperion Essbase System 9 Hyperion Financial Reporting Tutorial Qlikview Vs Others

Hyperion Essbase system 9 Blog April (1)

Information Warehouse

Dornakal's Hyperion Blog Download Hyperion Hyperion Consultant Blog Hyperion Documentation Hyperion Install Guide Information Management Mark Rittman Blog Oracle Essbase Tutorials SoftwareMag TWDI

Followers

Subscribe To
Posts All Comments Picture Window template by Josh Peterson. Powered by Blogger.