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

Best practices of the Physical layer


You've already learned that building the Physical layer of the repository is the first step in OBIEE 11g implementation and hence all the initial steps are not going to be covered. You are going to find the best practices of the Physical layer in this recipe. We're going to discuss the common mistakes in the Physical layer and learn how to have a successful implementation of this layer.

How to do it...

  1. Instead of creating the Physical layer objects manually, use the Import option from the File menu. Otherwise, we might make mistakes while specifying all the details about the physical tables.

  2. Circular joins shouldn't be used in the repository. Create aliases for each physical table to avoid the circular joins. You may create more than one alias for a single physical table.

  3. Be sure that physical joins exist in the Physical layer. Although it's possible to import the foreign key relations from the database automatically, we have to be sure that foreign keys...