Book Image

Oracle Business Intelligence 11g R1 Cookbook

By : Cuneyt Yilmaz
Book Image

Oracle Business Intelligence 11g R1 Cookbook

By: Cuneyt Yilmaz

Overview of this book

<p>Extracting meaningful and valuable business information from transactional databases is crucial for any organization. OBIEE 11g is a reporting tool that satisfies all the business requirements regarding complex reporting. It consists of a powerful back-end engine with a repository and a highly customizable graphical web interface.</p> <p>Oracle Business Intelligence 11g R1 Cookbook provides all the key concepts of the product including the architecture of the BI Server. This practical guide shows each and every step of creating analytical reports starting from building a well-designed repository. You will learn how to create analytical reports that will support different business perspectives. <br /><br />This practical guide covers how to implement OBIEE 11g suite in order to enable BI developers to create sophisticated web based reports. All of tasks will be covered step by step in detail. <br /><br />You will explore the architecture of the Oracle Business Intelligence Server and learn how to build the repository (RPD). We will also discuss how to implement the business rules in the repository with real-life scenarios.</p> <p>Best practices of a successful BI implementation are esssential for any BI developer so they are also covered in depth.If you are planning to implement OBIEE 11g suite, this step-by-step guide is a must have resource.All the key tasks are defined in detail and supported with diagrams and screenshots.</p>
Table of Contents (19 chapters)
Oracle Business Intelligence 11g R1 Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Implementing aggregate tables


In order to improve query performance, we have created aggregate tables at the database level. Now we're going to modify the Physical and BMM layers of the repository to gain benefit of summary data.

  • Physical layer: Aggregate tables should be imported and physical joins should be created

  • Business Model and Mapping layer: Secondary logical table sources are going to be added to the corresponding logical tables

  • Presentation layer: No modification will be made at this layer. Usage of aggregate tables will be transparent to the end users

How to do it...

  1. As we have already demonstrated how to import tables into the Physical layer in Chapter 1, Exploring and Building the Repository, you won't find every detailed step in this task. Here is the screenshot that shows the imported tables.

  2. The physical joins between the fact table and all three dimensions tables should be created. The first physical join is between FACT_SALES_AGG and DIM_SUBTYPE_AGG tables. The join condition...