BusinessObjects is a powerful ad hoc reporting and analysis tool. The single greatest component of BusinessObjects that will make your implementation succeed or fail is the universe. A universe is a business representation of your data warehouse or transaction database. It shields users from the underlying complexities of the database schema. BusinessObjects often refers to this as the semantic or metadata layer. In all your development efforts, you must stay focused on that purpose: business representation. If your universe becomes a glorified entity relationship model, your project will fail. If your universe includes every data element any user may possibly want from now to eternity, your project will fail.
Universes can become unwieldy for end users. Poorly defined joins will result in unnecessarily slow queries. The universe is the most important component to get right.
Keep It Simple
This universe was difficult for the administrator to maintain and was overwhelming even to expert BusinessObjects users. The result? End users often created invalid queries and blamed the data warehouse for bad data. Casual users would ask an IT expert to create MS Access data marts that were easier for them to use, thus defeating the flexibility and empowerment offered by an ad hoc query tool and causing unnecessary data reconciliation.
To build a successful universe, keep it simple. The universe should be useful for a clearly defined group of users and should not have much more than 200 objects in it. Bigger universes are technically feasible but not user friendly. Having more universes to build and maintain may result in slightly higher maintenance costs but will significantly increase end-user productivity and satisfaction. As your target user group expands, constantly ask yourself if the needs are distinct enough to justify a separate universe. If some users need only a handful of additional objects, keep it in the same universe. However, if they need many additional objects, create a separate universe.
Figure illustrates how different user groups will need access to different information. Human resources is one group of users that needs access to salary details but does not need product sales and order information. Therefore, a Salary universe will only have information from this one fact table. Marketing people may need information on sales but will rarely need information on the individual order numbers that customer service representatives need; however, customer service representatives need both order detail and summary sales. This is an example in which it may make sense to have one universe that meets the needs of both user groups (marketing and customer service representatives). A director of the marketing group is most likely a people manager and may need salary and employee details; the director would use two universes, as including three subject areas in one big universe would potentially be overwhelming for the majority of users who don't need this information.
Share This
About BO
About Blog
DW Blogs
BI Portal
ETL Process
DW Basics
DW Comparisons
Ab Initio Blog
1010data Blog
Actuate Blog
Autosys Blog
BO Blog
Cognos Blog
DataStage Blog
Hadoop Blog
Informatica Blog
Greenplum Blog
MapReduce Blog
MicroStrategy Blog
Netezza Blog
Oracle Blog
Pig Blog
QlikView Blog
SAS Blog
Teradata Blog
WebFOCUS Blog
Zookeeper Blog
Big Data Analytics
As you add and modify reports and their components, you should periodically save the document. To save a document, click the Save button on the toolbar or select File | Save from the pull-down menu. This saves the document.rep file to your local disk or work group directory. Any changes you make to a query, the results of the query, as well as the individual report tabs and blocks are saved in this one document.rep file. If you make a lot of changes to the document, you may want to use File | Save As to give the document an entirely new filename. This way, you can safely revert to a previous version of the document.
Save As
Using File | Save As also allows you to select a different file format for sharing data with other applications. In the Save As Type box, click the drop-down box to see the different file types. BusinessObjects will automatically replace the .rep extension with a new extension for the corresponding file type.
When you need to share documents with other users who may not have access to BusinessObjects, consider saving them as Portable Document Format or .pdf. This allows any users with Adobe Acrobat to read the report. Adobe Acrobat is a third-party software program that many people have installed and use for viewing and printing corporate and/or Internet documents. When you save a BusinessObjects document as a .pdf file, it converts the report tabs to Bookmarks in Adobe, allowing readers to easily navigate between the different reports.
Save As HTML
Save As HTML is useful for publishing corporate documents to an intranet, to InfoView, or to the Web. When you choose File | Save As HTML, BusinessObjects prompts you with additional options. These are the Save options:
Current Report Converts just the current report tab to an HTML page.
All Reports in Document Converts all report tabs to HTML.
Select Reports Interactively choose the report tabs to convert to HTML.
BusinessObjects Document Allows BusinessObjects full client and three-tier mode (ZABO) users to download a copy of the document.rep file. Creates a Download hyperlink in the HTML page. Warning: it does not save the original document.
When you save a document as HTML format, BusinessObjects generates multiple folders and files. For each report you save as HTML, BusinessObjects adds a hyperlink within the HTML page.
Save Options
You can modify certain options for saving a document. Select Tools | Options, then the Save tab. Alternatively, select File | Save As and click Options.
Application Options apply to all documents:
Prompt for Document Properties Document properties include a Title (which can be different from the filename), Subject, Keyword, and Comments. This additional information is useful in providing help and/or documentation about the reports that you can view through File | Properties. Check this box to have BusinessObjects prompt you for additional information when you first save a new document; it will not prompt you with subsequent saves. I recommend checking this option.
Automatic Save Every
Minutes Use this if you want BusinessObjects to save your work automatically, after N minutes.
Options for Current Document apply only to the active document:
Refresh Document When Opening Causes all data providers/queries to refresh when you first open the document.
Protection Password If you enter a password here in the save options, you will be prompted to enter a password prior to opening a document. BusinessObjects will prompt you to confirm the password you enter. I do not recommend file-level password protection, as you will have no way to recover the document if you forget the password.
Write Reservation Password Report readers can open password-protected documents as read-only. If you want them to be able to save formatting changes or refreshed result sets, then you must also assign a write reservation password.
A master/detail report is a particular kind of report in which a dimension value is used to separate different blocks. Master/detail reports allow you to analyze data within a particular subset. For example, you can have multiple tables, charts, or crosstabs for each color of wine. As discussed earlier in “Sections” and shown in Figure , BusinessObjects will insert a subsection when you create a master/detail report.
From Report Window
When your block already contains the data you want to use as a section heading, you can convert an existing column to a section heading called a master cell.
Right-click the cell that you want to convert to a section heading. In the following crosstab, you want color to become a section heading. There will be two sections, one for Red wines and one for White wines.
From the pop-up menu, select Set As Master.
BusinessObjects moves the cell from the block to a new cell that acts as a section heading.
From Report Manager
If you want the dimension column to remain in the block, but you want a section heading in addition, use the Report Manager to create the master/detail report.
From the toolbar, click Report Manager or select View | Report Manager from the pull-down menu. 
Ensure the Report Manager is set to Data view. If you have multiple data providers, click the Data Provider radio button at the bottom of Report Manager to sort the variables by query.
Under Variables, select the dimension object you want to become the section header and drag it to the Report window at the upper-left corner of the block. The mouse changes to an insert cell cursor, and the status bar indicates you are creating a new section.
BusinessObjects allows three block types: table, crosstab, and chart. A master/detail is a type of report or section and not specifically a block style. Financial is a block type available in WebI; in BusinessObjects it is considered a way of formatting a table block. Frankly, this distinction is a little confusing, but it only matters when you are trying to format a block. A report can contain multiple block types. Figure, for example, has both a chart block and a table block within one report. The following table summarizes the different block types and when to use them:
You can choose to add, modify, and delete blocks and reports either through the Report window or Report Manager. In the following examples, I will show how to use either approach.
Table
When you initially create a new document, BusinessObjects uses the default block type of table. A table is a spreadsheet-style block that lists data in rows and columns. When you are working with an existing document, you can choose to:
Insert a table into a new report or report tab
Convert a crosstab or chart block to a table
Insert a table into an existing report
Inserting a Table into a New Report
In this example, you will create a new report and insert a table through the Report window.
Use the pull-down menu to select Insert | Report.
BusinessObjects inserts a new report tab, named ReportN, where N is a sequential number. If you have one report tab, BusinessObjects creates Report2. When your report tabs contain meaningful names, as in the following example, BusinessObjects restarts the numbering. To modify the name of the report tab, double-click the tab and enter a meaningful name.
The Report window is initially blank. From the pull-down menu, select Insert | Table. Or, if the report toolbar is displayed, click Insert Table.
BusinessObjects converts the mouse pointer to a table icon. Drag the mouse to indicate where you want to position the table.
BusinessObjects presents you with the New Table Wizard. From here, you can choose to insert a table with data from the existing document, a new query on the existing universe, or a new query with a new data source. Select Use Existing Data From The Document.
The New Table Wizard displays a list of variables from all data providers. When you have multiple data providers in a document, click By Data Provider to view the variables by query rather than alphabetically. Use CTRL-click to select which columns you want to appear in the report table. In the following example, I want a table listing the Country and Average Rating:
Click Finish to close the New Table Wizard and have BusinessObjects insert the new table. At this point, the table is fairly basic. 
Converting an Existing Block to a Table
If you have a report that contains a block and you want to view the same data in a different format, you can convert the block to a different type. In the following example, you will convert a chart to a table. You can also convert a small table to a chart. Use the Report Manager to ensure you have selected the correct block.
From Report Manager, set the view to Structure by selecting the Map tab and clicking the Structure icon at the bottom.
Select the report tab that contains a chart—in this example, RedWinesChartByCountry.
Within the Report Manager Map, select Chart1. Note that the chart block is correspondingly selected in the Report window. Right-click to invoke the pop-up menu and select Turn To Table. Note that the status bar tells you it will turn the chart into a table. 
BusinessObjects replaces the chart block with a table block. The section headings by Color remain the same. Note that in the Report Manager window, the block type also now reflects Table 1.
Chart
Charts are a powerful way to uncover trends and patterns in your data. In many BusinessObjects deployments, charts are underutilized. Perhaps this is in part because a number of deployments grew out of replacements of mainframe or transaction-based reporting systems that do not provide charts. Also, many times, report readers do need to see the individual numbers. However, I would argue that a corresponding chart can help you take your analysis one step further to uncover opportunities and potential improvements and, therefore, recommend that all standard reports contain at least one chart. Table provides some sample business questions to show which block type best answers certain questions.
Table : Sample Business Questions that Can Best Be Answered by a Particular Block Type 
Inserting a Chart
As with tables, you can convert an existing table or crosstab to a chart, or you can create a chart based on a new query. Because charts generally involve fewer variables than tables and crosstabs, I rarely use Convert and recommend using Insert | Chart.
In this example, you will create a new report and insert a chart through the Report window. You could also create a chart within an existing report to have multiple block types within the same report.
Use the pull-down menu to select Insert | Report. BusinessObjects inserts a new report tab. Or, if the Report toolbar is displayed, click Insert Chart.
Double-click the report tab to enter a meaningful name and press OK.
From the pull-down menu, select Insert | Chart.
BusinessObjects converts the mouse pointer to a chart icon. Drag the mouse to indicate where you want to position the chart.
Note With tables, BusinessObjects automatically resizes the box you initially draw to fit all the columns in the table. With charts, it does not resize the box, so ensure that the size of your box is adequate for the number of columns or data points.
BusinessObjects presents you with the New Chart Wizard. Select the radio button Use existing data from the document.
The New Chart Wizard displays a list of variables from all data providers. When you have multiple data providers in a document, click By Data Provider to view the variables by query rather than alphabetically. Use CTRL-click to select which columns you want to appear in the chart. For most chart types, you want to limit the number of dimension objects but may have multiple measures.
The New Chart Wizard prompts you to select a chart type. For each chart type, there are different styles and settings, which are discussed further. Select the desired type and style.
Click Finish to close the Wizard and see the newly inserted chart. The chart shown here is fairly basic
Crosstab
A crosstab block allows you to compare information by different groupings and transposes what may originally be rows in a tabular report to column headings. People frequently use crosstabs for the following types of analysis:
Customers sales by year, quarter, or month
Financial measures by actual and budget
Product sales by region
Caution Columns and Rows are mislabeled in the BusinessObjects Pivot tab. So if you really want Year to appear as column headings in your crosstab, then you place this variable under Rows. Because of this confusion, I recommend using the Slice and Dice Panel in which you drag and drop the variables to create a crosstab .
The columns may have multiple levels
You can either convert an existing table or chart to a crosstab or you can insert a new crosstab based on new data. In the next example, you will convert an existing table to a crosstab. The initial table contains the dimensions Color, Varietal, and Country and the measure Average Price. You want to create a crosstab to compare how prices vary by country for each varietal.
From within the Report window or Report Manager, select the table block.
Right-click to call the pop-up menu and select Format Table. Alternatively, use the pull-down menu to select Format | Table.
Select the Pivot tab from the Table Format dialog box. Under Available Variables, BusinessObjects displays all the variables in the microcube. Under Used Variables, Body, BusinessObjects displays the columns from the existing table.
Click Apply. BusinessObjects converts the table to the following crosstab:
Data Manager allows you to view the components of a query in business terms as well as the query results in plain text.
To access Data Manager, click View Data from the toolbar or select Data | View Data from the pull-down menus.
In the next example, there are two queries within this one document. Click the + next to each data provider to see the columns included in the particular query. Notice that at this stage, you see only the result objects that make up the columns of data; you do not see the conditions that may be different for each query. Query 1 contains additional details by Varietal and Price that are not included in Query 2. Data providers are explained in more detail.
Data Manager initially displays the query results for the first query. You can scroll right and left to see more result columns. Alternatively, you can adjust the column widths. These column widths do not relate to column widths within a formatted report; they simply allow you to see more result columns within the Data Manager window. To adjust the column width, position your mouse on the crossbar between each column heading. The mouse turns to a column-sizing cursor.
Another point to notice in the Data Manager is that it contains detailed data. The reports, on the other hand, may contain summary information that uses Projection Aggregates set by the universe designer. For example, in Figure , the Average Rating for French Red wines is shown as 84.66. BusinessObjects calculates this average from all the individual rows for each Vintage, which exists in the result set but which is not displayed in Figure . When your summary reports appear incorrect, it’s helpful to look at the raw details in the Data Manager to understand if there is an error in the source data, the query definition, or your report calculations. Data Manager allows you to export to Excel detail queries that may not otherwise be displayed in a formatted report.
The Definition tab of Data Manager displays additional information about each query, including the number of rows returned, time to refresh, and schedule information. When you select a variable rather than a query name, you see the variable type (dimension, measure, detail) and the values. You use Data Manager to link variables from multiple data providers.
Report Manager is a tool that allows you to view and modify the components of each report. You can view the data variables, or you can view the structure of the report.
Data View
To display the Report Manager, click the Report Manager button from the toolbar or select View | Report Manager from the pull-down menu.
BusinessObjects displays the Report Manager in Data view. By default, Report Manager is anchored to the toolbar. You can drag and drop it to any place on the screen. Under Variables, all the variables in the microcube are listed alphabetically. Notice in the following screen that Vintage is a variable within the microcube, but Vintage is not displayed in the chart or table. You can add the variable to the block by dragging it from Report Manager to the block. Also, because this document contains two queries, there are two variables for Color, each from a different query. In this case, the contents for this variable are the same, but in other circumstances, they could be different. For example, Query 1 could contain a condition Where Color=Red and Query 2 could contain a condition Where Color=White.
To sort the variables by data provider rather than alphabetically, click the Data Provider icon from within Report Manager.
Map View
To switch to Map view, click the Map tab from within Report Manager. Initially, Report Manager shows a list that corresponds directly to the report tabs within the Report window. The Navigation icon in the bottom-left corner is selected. Navigation allows you to select individual reports within the document, or for master/detail reports, the individual sections.
To view the components of an individual report in Structure mode, click the Structure icon in the bottom-left corner. The Report Manager displays the structure of the first report tab, while keeping the WYSIWYG format in the Report window, as shown in Figure . Notice that this report has one main section. Within the main section, there are two blocks (a table and a chart) and one cell that contains the picture of the wine glass. The Map view shows the different block types of table, chart, and crosstab with unique icons and names. As you select each report component within Report Manager, BusinessObjects highlights the corresponding component within the Report window. This feature is excellent for formatting different report components. Within Report Manager, Map mode, you can right-click any component to call a pop-up menu with various formatting functions. Map mode also makes it clear which components belong to a block or to a section: note that within the chart block, there is a title, but it belongs to the individual chart and not the entire report; if you delete the chart, you delete the title as well. 
Recall from the earlier discussion of sections that a master/detail report adds a subsection to the main section. This is more apparent when using Report Manager to view the structure, as shown in the following screen. The subsection name is based on a dimension variable for which you want a separate block (table, chart, crosstab); in this example, Color Section. Within the Color section there is a master cell that contains the contents for each new color; there is also a crosstab or details for each new color. In the Report window, you see two section cells and two crosstab reports, for Red and White; in the structure, there is only one “placeholder,” regardless of how many different dimension values may exist for the master cell. 
Within a given report, you have several components: sections, blocks, and cells. As you explore information within a report, these components are not particularly important; as you try to format the report or add information to it, however, it’s important to understand which component you are altering.
Sections
Every report has a main section. Within the main section, you can have a section header and a section footer; these are different from page headers and footers that appear in printed reports. Main section headers typically hold the title of the report but also may contain a picture or logo. Reports also may have subsections if you create a Master Detail report. Figure shows a report with section headers for each different color of wine. The report title “Average Wine Ratings By Country and Decade” appears in the main section.
Blocks
A block is a set of data that contains column headings, row headings, and data values. A block also may contain titles for an individual table or chart, different from a title that applies to the entire report (main section). BusinessObjects supports different types of blocks such as a simple table, crosstab, or chart. A block is one component within a section.
Variables and Cells
A cell contains either fixed text, formulas, or report variables. Cells that contain fixed text such as a title or a picture are referred to as constants; the contents of the cell never change no matter which data you are viewing. Cells whose contents change may be either a formula or a report variable. Report variables are pointers to the columns of data. When a report author builds a query, the author selects objects from the universe. These objects become variables in a report. There are three types of report variables that correspond directly to how the universe designer defines an object:
A dimension object is denoted with a blue cube and is typically textual information by which you sort and analyze numeric measures. In the wine reports shown thus far, color, vintage, varietal, and country are all dimension variables.
A measure is a number that you want to analyze; it is denoted by a pink sphere or circle. Average Rating and Average Price are measure variables.
A detail provides additional information about a particular dimension. You may want to see the information in a list report but will not want to use it to analyze measures by. Phone number and street address are typical detail variables.
In a spreadsheet, each cell contains the actual value. In a BusinessObjects document, the cell contains either the constant value or a formula that tells BusinessObjects where to find the data value. By viewing the report structure, you can see the true contents of each cell, as shown in Figure To view the report structure, use the pull-down menu to select View | Report Structure.
The first cell is a text cell whose contents do not change, referred to as a constant. All the other cells show formulas that are used to retrieve the data values for each report variable. For example, the following formula will retrieve the individual colors of Red, White, and Rose:
=
One of the hardest concepts with BusinessObjects is the document itself. A document is not a simple report, but rather, a set of components that eventually present a report. A document contains the following components:
One or more data providers that are typically SQL queries that extract information from source databases.
A result set in which the results of the queries are stored as a microcube. You can view the results through Data Manager.
One or more formatted reports. Each report may be a different type, such as a chart, table, or crosstab. One report may have multiple report types.
Figure gives a conceptual overview of a document that is made up of two data sources: a SQL query and a spreadsheet. The document contains three reports, two that are tabular reports with a view to each result set and a third that displays a chart with data from both result sets. In many documents, you may have only one query, one result set, and one report. Alternatively, you may have one query, one result set, and multiple reports. Each report tab may contain a view with the full data set but in a different block type such as table, crosstab, or chart. Alternatively, each report may contain a limited number of columns or rows of data as you remove variables and apply filters. The structure of the BusinessObjects document allows you to explore information from multiple perspectives without ever having to requery the database. Similarly, the microcube technology allows you to seamlessly combine information from multiple data sources into one report, even if you don’t have a central data warehouse.
Figure shows the initial BusinessObjects interface. By default, only the Standard and Formula toolbars are displayed. Notice that there are three report tabs, each with a different report name and view to the data. To navigate to a new report, click the desired report tab.
The Status Bar
The status bar at the bottom of the BusinessObjects screen changes depending on what actions you perform on a document. If you refresh a query, it will display the progress of the query from analyzing to fetching. As you drag and drop cells or convert blocks to different formats, the lower-left corner of the status bar tells you what action will occur. The right side of the status bar tells you the last time the query executed and will warn you if the query did not run to completion.
View Options
You can modify view options to alter the way BusinessObjects displays documents. View | Page Layout will show the print header and footers. View | Structure will show the contents of a report with cells that contain formulas (see Figure 16-6 for an example). Structure mode is useful when you are trying to format large documents. View | Grid will display a grid behind the report components. This is useful for aligning different components. These different view options act as toggles to turn the modes on and off. 
Toolbars
The toolbars enable you to access commonly used functions through buttons. By default, BusinessObjects displays the Standard and Formula toolbars. To have BusinessObjects display additional toolbars, select View | Toolbars and check the appropriate boxes.
The option Large Buttons will increase the size of the icon on the toolbar. Show Shortcut Keys In Tooltips will display the keyboard shortcut when your mouse moves over a particular button. For example, in Table, CTRL-O is a shortcut to open a document. Tooltips display the purpose of a particular button. Notice in the next button that BusinessObjects shows the tooltip (Open) as well as the shortcut (CTRL-O). Table lists buttons on the Standard toolbar. Other toolbars are reviewed in different chapters as they are used.
Buttons on the BusinessObjects Standard Toolbar 


A document is a file that contains formatted reports, charts, query definitions, and a subset of data from one or more data sources. A document is your starting point for viewing and analyzing data or for modifying a standard report. BusinessObjects full-client documents use document.rep as the file naming convention, where document can be a long report name and .rep is always the extension. Other Business Objects products such as WebI documents and Business Query for Excel have different file extensions.
BusinessObjects documents can be stored in several places:
1.A personal directory on your local computer’s hard disk or a work group directory on a file server
2.The document domain of the BusinessObjects repository
3.E-mail
Where the document is stored affects how you open a document.
Specifying the Default Directory
When you open a document or retrieve a document from the repository, BusinessObjects looks first in a default directory. The default directory for BusinessObjects reports is
\Business Objects\BusinessObjects 5.0\UserDocs
You can change the default directory for storing and retrieving documents.
From the pull-down menu, select Tools | Options, then click the File Locations tab.
Under File Types, double-click User Documents or highlight User Documents and click Change. This launches a standard Browse For Folder dialog box. Click through the various directories and select the desired default folder.
Click OK to close the Browse For Folder dialog box, then OK again to close the Options.
Opening a Local Document
To open a document from the default directory:
Select File | Open from the pull-down menu.
When you use the pull-down menu, BusinessObjects will display the last five reports you accessed. Click the name of the report you want to open.
Alternatively, you can:
Click the Open button on the toolbar. BusinessObjects displays a standard Open dialog box.
Select the name of the file you wish to open. If you want to open more than one document at a time, CTRL-click to select multiple files.
Repository Documents
A report author may distribute documents via the repository, document domain in several ways. First, if there are only a few report readers for the document, the author may send the document to one or more users or groups of users. The report author may schedule the report to be refreshed and distributed on a periodic basis by Broadcast Agent. Once the query is refreshed, it gets stored in the document domain. Finally, the repository can contain a set of documents that an author has published for all users as Corporate Documents. In all cases, in order to access these documents, you must first retrieve them from the repository, then open your local copy, as shown in Figure.
Documents from Users
To open a document a report author has sent you, select File | Retrieve From | Users.
BusinessObjects displays a list of reports that users have sent you, who sent the report, the time exported to the repository, and the approximate file size. Note under the column Type that all Types are User documents.
The list of available reports can become quite long. If you want to filter the list according to certain groups of reports, called Categories, check the box Show Only This Category Of Documents. By default, BusinessObjects will initially display documents that have not been associated with a particular category, 
For additional search options, click More >>. BusinessObjects expands the Retrieve panel to include a Find Documents section. Within Find Documents, you can search for documents by the different ways it was exported to the repository, specific document domains, or particular document characteristics such as the size of the file or universe accessed.
Highlight the name of the document you wish to retrieve and open. To retrieve and open multiple documents, CTRL-click.
Tip At this point, you could also right-click the individual document to Retrieve Into a different default directory or to view additional properties about the document.
Check the box Open On Retrieval to have the document automatically opened once you have retrieved it from the repository.
Click Retrieve. BusinessObjects transfers the report from the repository to your local disk.
When the document has been transferred, BusinessObjects tells you the import was successful and opens the document. Click OK to acknowledge the message.
Scheduled Documents
Broadcast Agent (covered in Chapter 20) allows you or report authors to refresh documents on a periodic basis. Once the document has been refreshed, Broadcast Agent will store the results in the repository, document domain. To retrieve documents from Broadcast Agent, you follow the same process as User Documents, but use File | Retrieve From | Broadcast Agent as your first step. The document Type will display Processed documents, rather than User documents. Continue with steps 3–8 in the preceding section.
Corporate Documents
Corporate documents are documents that all users can access. Documents may be restricted to particular groups, but not to particular users. InfoView users also may access Corporate documents, so in this list, you may see different document types, including WebI documents.
BusinessObjects administrators build universes using Designer. The key components of a universe are classes, objects, tables, joins, and contexts. As shown in Figure, classes and objects are the main items a business user sees when building a query. Objects become individual columns in a report; classes never appear in a report.
Classes
Classes are a way of grouping individual objects. In Figure, these appear with a folder icon. Sometimes these relate closely to the tables in a database but should be regrouped into business topics. In the sample EFASHION universe, the class Product is a more meaningful business term than Article and includes items from multiple tables ARTICLE_LOOKUP and ARTICLE_COLOR_LOOKUP.
Objects
Objects refer to columns of data. There are different types of objects (as explained further in Chapter 8) denoted with a square, sphere, or triangle icon in Figure 5-2. Objects can include a significant amount of intelligence and may not relate directly to one column in the database. For example, the object Sold At (Unit Price) includes a calculation of revenue/quantity. However, to avoid divide by 0 errors, it also includes an if-then-else statement to check for 0 quantities. This is one example of why Business Objects universes are so powerful and a much better alternative to providing users with direct access to tables; if-then-else statements in SQL are implemented differently for each RDBMS and are not something most users would know how to write.
Tables, Joins, and Contexts
Report authors never directly see several core elements of a universe: tables, joins, and contexts (see Figure). Universe designers use tables to map data from fields to objects in the universe. Joins allow the use of more than one table in a report, and contexts resolve which join path to take when more than one path is possible. All three of these components are then combined to dynamically build SQL statements in BusinessObjects.

Tables
Tables are individual database tables that provide data. A table may be a physical table in the RDBMS, or it may be a view or synonym. Further, Designer provides functionality to create aliases that are treated like tables.
In a data warehouse or data mart environment, you will have two types of tables: 1) a fact table that contains numeric information and 2) dimension tables that allow a user to analyze the numeric data from different perspectives such as product, time, or geography. The fact table can have millions of detailed rows of data or can be smaller, with summary numbers. One fact table together with its associated dimension tables is referred to as a star schema. There can be multiple fact tables and star schemas within a universe.
Dimension tables are also referred to as lookup tables or reference tables. The dimension tables can be broken into more than one table; for example, detailed material IDs may reside in a MATERIAL_ID table. The groupings and product hierarchy for the material IDs may reside in a separate table such as PRODUCT_GROUPING. This type of structure, referred to as a snowflake design, is used in some data warehouses that have extremely large dimensions as well as certain ROLAP tools.
In a normalized OLTP, both the fact tables and the dimension tables may be spread across many tables. For example, order information may exist in both an ORDER_HEADER table and an ORDER_LINES table. Dimensions and hierarchies often do not exist in the OLTP (note in Figure that there is no Time or Plant table, just the individual facility that produced the product). Only the individual material IDs, customer IDs, and so on, are stored with detailed records. BusinessObjects does not allow a universe to point to two different databases, so having data that users want to analyze together generally calls for a data warehouse or data mart. However, if this is not immediately possible, BusinessObjects provides a workaround in the end-user tool. You, as the designer, can create two separate universes: one that points to the OLTP and one that points to the dimension database. Users then would have to build two queries; however, as long as the detailed key information is named consistently between the universes, the results will be nicely displayed in one table, without the user having to manually stitch the two result sets together.
When you build a universe, you are not replicating any data from these tables. Instead, you are basically creating pointers to tell BusinessObjects where to find the data; no data is stored in the universe itself. This is a drastically different approach than a full MOLAP tool such as Hyperion Essbase, Cognos Powerplay, or Microsoft Analysis Services. Data gets replicated only when a BusinessObjects user launches a report and the RDBMS sends results back to the report, populating a micro cube in a .rep file on either the WebI middle tier or the Windows client.
Joins
Joins specify how tables, views, synonyms, or aliases relate to one another. Joins allow a user to combine information from two or more tables. For example, in the following diagram, there are joins between ORDERS_FACT and the dimension table PLANT as well as between ORDERS_FACT and the dimension table PRODUCTS. There are no joins to the SUPPLIERS table. Without this join, a user is not able to determine which suppliers provide various products. There are many types of joins.
Contexts
Contexts group related joins. A context may group a set of joins together for each star schema. Without contexts, BusinessObjects would generate SQL that contained a loop. Loops generally result in incorrect queries with fewer rows returned than expected. Earlier versions of BusinessObjects supported queries that contained only one context. As contexts were generally confusing for end users, they were best avoided. BusinessObjects now allows one query to generate multiple SQL statements, one for each context. This allows users to query multiple star schemas to create powerful business reports. Two examples follow.
Days Sales Inventory (DSIs) How many days worth of inventory do you have according to the daily sales volume? As shown in Figure, this query would involve two contexts, one with all the joins for the star schema with a SALES_FACT table and a second context with all the joins related to INVENTORY_FACT.