List of Figures

 < Day Day Up > 



Chapter 1: Introduction to Business Intelligence

Figure 1-1: Each function had its own custom-built transaction system.
Figure 1-2: The business intelligence explosion
Figure 1-3: ERP systems ensure data integration and apply process rules.
Figure 1-4: Business Objects’ growth has outpaced BI market growth.
Figure 1-5: Business intelligence architecture
Figure 1-6: Major product innovations

Chapter 3: Segmenting Your Users

Figure 3-1: Many people besides direct users affect the success of a BusinessObjects implementation.

Chapter 5: Universe Design Principles

Figure 5-1: A universe is a business representation of the database based on the needs of target user groups.
Figure 5-2: Business users see classes and objects from the Query panel. The Price objects have been placed under the Product class but could also have been placed under Measures.
Figure 5-3: Tables, joins, and contexts are core elements of a universe that only the administrator sees in Designer.
Figure 5-4: Business Objects supports star schemas, snowflake schemas, and normalized table structures.
Figure 5-5: A context groups a set of tables into one star schema.
Figure 5-6: Process overview of how Designer interacts with the Business Objects repository
Figure 5-7: A company may have one person that modifies the universes globally but the BusinessObjects repositories are located in different regions.

Chapter 6: Using Designer to Build a Basic Universe

Figure 6-1: In this scenario, there are two sets of user IDs and passwords involved in BusinessObjects: the BusinessObjects login and the source system database login.
Figure 6-2: In the second scenario, there are three sets of user IDs and passwords involved: the repository connection, the BusinessObjects logon, and the data warehouse access.
Figure 6-3: Strategies uses SQL to read the data dictionary tables.
Figure 6-4: Object strategies propose the initial classes and objects and require nine columns of information. Consider creating an object strategy using spreadsheet data from a JAD session.
Figure 6-5: Join strategies propose joins between tables and use five columns of information. Three are required, two are optional.
Figure 6-6: Table or structure strategies require six columns of information and are used to provide information in the structure window of the universe.
Figure 6-7: SQL may give incorrect results if you try to use a GROUP BY function such as SUM across two tables that have different numbers of rows. To prevent this inaccuracy, check the box Multiple Select Statements For Each Measure in the universe parameters.

Chapter 7: Universe Joins

Figure 7-1: This sample Oracle sales history universe shows table sizes, key names, and cardinalities. This information is useful in defining joins.
Figure 7-2: Users receive this error message if you do not resolve loops or allow contexts in File | Parameters, SQL tab in Designer.
Figure 7-3: BusinessObjects automatically generates a Select statement for each context.
Figure 7-4: This table shows that Customer_id and MM_YY together uniquely identify each record as customer names and addresses have changed over the years.
Figure 7-5: In older versions of BusinessObjects, one could create complex joins with multiple join statements. This kind of join will give a false loop detection in version 5.
Figure 7-6: With aliases, the data model no longer contains a loop. The alias name replaces the physical table name in parentheses.
Figure 7-7: Steven King does not report to a manager. Neena Kochhar, Lex De Haan, and others are managed by Steven King.
Figure 7-8: Shortcut joins provide BusinessObjects with an alternate, faster join path without creating a loop.

Chapter 8: Classes and Objects

Figure 8-1: The Universe pane shows classes and objects that appear to users when they build a query.
Figure 8-2: Inventory and account balances should be aggregated but not by time.
Figure 8-3: The parameter Colsort=3 sorts columns alphabetically (left), whereas the parameter Colsort=13 sorts columns by the order in which they exist in the physical table (right).
Figure 8-4: SQL groups individual rows into common columns, reducing the number of rows of data sent to the client.
Figure 8-5: A BusinessObjects projection aggregate groups records within the report.

Chapter 9: List of Values

Figure 9-1: A list of values query is associated with an object in the universe. It queries the dimension or lookup tables in the RDBMS to present users with a pick list for conditions in a user query.
Figure 9-2: Customers reside in cities that are part of countries. Marketing and sales personnel may manage more than one country.
Figure 9-3: Adding Country as a prompt in the Customer Id list of values involves four tables.
Figure 9-4: Sending Plant Id and Receiving Plant Id share the same list of values query, PLANTID.LOV.

Chapter 10: Advanced Objects

Figure 10-1: The SQL Editor helps you write SQL statements.
Figure 10-2: Create interactive objects with @Prompt
Figure 10-3: Two sample dimensions showing the number of potential rows at each level
Figure 10-4: Aggregate tables are summary tables that allow for faster queries.
Figure 10-5: A detail fact table and a summary aggregate table may share some of the same dimension tables.
Figure 10-6: Quarterly sales report

Chapter 11: Multidimensional Analysis

Figure 11-1: The Time Dimension and the Product Dimension each have four levels that make up a hierarchy.
Figure 11-2: When a WebI user drills through to the detail fact table, the user selects a document; the intersection in the MOLAP cube is passed into the WHERE clause of the query.
Figure 11-3: The UDS Designer maps relationships between the MOLAP cube metadata and the universe classes and objects.
Figure 11-4: The Essbase Outline and the BusinessObjects Classes and Objects have common elements that become the Translation Map.

Chapter 12: Incorporating Supervisor Settings into the Universe Design

Figure 12-1: A department at the upper level is called an ancestor, and its children are descendants. Each user can be defined to one or more groups; each copy of a user is called an instance.
Figure 12-2: Resources such as universes, documents, stored procedures, and timestamp settings get linked at each group. The descendants inherit access to these resources.
Figure 12-3: Groups and users are linked to resources in Supervisor. Each user has a profile that determines which software and menus the user sees.
Figure 12-4: Groups inherit rights from ancestors; Accounts Receivable inherits access to universes linked to the ancestors Finance and Plastics Express.
Figure 12-5: Ancestors do not inherit rights from descendants. The Finance group has not inherited a link to the universe ACCTREC.UNV.
Figure 12-6: The Sales and Marketing organization is organized by product categories and regions; row restrictions allow data to be automatically filtered according to this organization.
Figure 12-7: All data is still available in the database, but a WHERE clause will filter the data so that each person sees only the rows he or she needs.
Figure 12-8: The top pull-down menu and toolbar uses the Reader Predefined setting and has fewer options than the bottom pull-down menu and toolbar, which uses the Default Predefined Setting.

Chapter 13: Design Principles: Where to Put the Intelligence

Figure 13-1: Intelligence can be built in a number of places in a BusinessObjects deployment.
Figure 13-2: In a BusinessObjects full-client deployment, users drill within reports and not the MOLAP cube.
Figure 13-3: In a thin-client deployment, users drill against the MOLAP server via formatted reports and charts.
Figure 13-4: Hyperion Essbase handles much of the intelligence with simple toggles and no complex programming.
Figure 13-5: Percentages and ratios require a two-step calculation that MOLAP tools easily handle.
Figure 13-6: Creating a role of report reviewer can help companies minimize the risks of unnecessary and inconsistent report formulas.
Figure 13-7: Deciding where to put the intelligence is a series of trade-offs.

Chapter 14: Minimizing Universe Maintenance

Figure 14-1: Linked universes help ensure consistent dimensions across universes.
Figure 14-2: Linked universes allow universe creation to be decentralized yet still consistent.
Figure 14-3: Two repositories allow designers to separate development and production environments.
Figure 14-4: Domains allow separation of test and production universes and documents.
Figure 14-5: BusinessObjects Metadata Bridges allow metadata in two leading ETL tools to be shared with the BusinessObjects universe.
Figure 14-6: BusinessObjects Universal Metadata Bridge enables designers to build universes from any tool that supports XMI.

Chapter 15: Almost There

Figure 15-1: Print parameters displays all the settings in File | Parameters.
Figure 15-2: The Full Description of the object shows object properties and object formats, whereas the list gives only the object name.
Figure 15-3: List Component Contexts gives a list of the context, whereas Full Description Context gives the joins that belong to the context.
Figure 15-4: Universe development follows an iterative process.
Figure 15-5: Process overview of a BusinessObjects query

Chapter 16: Introduction to Reporting

Figure 16-1: Users log into a repository to access universes and documents.
Figure 16-2: To open documents stored in the repository, first retrieve the documents, then open the local copy.
Figure 16-3: The BusinessObjects workspace
Figure 16-4: A BusinessObjects document is composed of several components.
Figure 16-5: Every report has a main section; a master/detail report also has a subsection.
Figure 16-6: Structure view shows the individual components of a report and how cells contain variables, not individual data values.
Figure 16-7: In Map mode, Report Manager allows you to view the structure of a document while simultaneously viewing the WYSIWYG format in the Report window.
Figure 16-8: Tabular versus crosstab report blocks

Chapter 17: Report and Chart Formatting

Figure 17-1: Format Cell, Number tab
Figure 17-2: Format Cell, Alignment tab
Figure 17-3: Cell Format, Border tab
Figure 17-4: Cell Format, Appearance tab
Figure 17-5: Select components of a table prior to formatting
Figure 17-6: Alerters allow you to highlight rows according to formulas and conditions.
Figure 17-7: Table Format, General tab
Figure 17-8: Table Format, Page Layout tab
Figure 17-9: Chart components
Figure 17-10: Chart AutoFormat provides several chart types with popular formatting options.
Figure 17-11: Chart Format, Series tab allows you to specify different formats for each measure.
Figure 17-12: Charts can have two Y axes.
Figure 17-13: Standard report styles define formatting options for all report components.

Chapter 18: Analyzing the Data: the Slice and Dice Panel

Figure 18-1: The Slice and Dice Panel enables you to analyze data.
Figure 18-2: Breaks group the data into what appears as mini-tables.
Figure 18-3: The Slice and Dice Panel and a formatted report with multiple sorts, breaks, and calculations
Figure 18-4: Complex Filters allow you to filter rows according to formulas.
Figure 18-5: Outline view allows you to analyze subtotals for individual sections.
Figure 18-6: Build crosstab reports via the Slice and Dice Panel.
Figure 18-7: Euro Exchange Rate table
Figure 18-8: The Formula Editor helps you write complex formulas.
Figure 18-9: Calculations in columns and footers are reevaluated according to their context.

Chapter 19: Exploring the Data: Multidimensional Analysis

Figure 19-1: Understand the hierarchical nature of your dimensions before drilling within a report.
Figure 19-2: The document or microcube may contain more data than what is initially displayed in the report, allowing you to explore the data without generating a new query.
Figure 19-3: Projection aggregates recalculate summary and detail numbers with each drill. Projection aggregates are set by the universe designer for each measure.
Figure 19-4: Snapshots create a picture of an analysis at a particular point in drilling around.
Figure 19-5: Scope of Analysis modifies the query to include more data in the microcube for drilling.

Chapter 20: Accessing New Data

Figure 20-1: Refreshing a query sends SQL to the data source.
Figure 20-2: A customized list of values can be viewed in Tabular or Hierarchical format.
Figure 20-3: Broadcast Agent actions
Figure 20-4: BCA scheduling options
Figure 20-5: BCA distribution options
Figure 20-6: Use the Console to view the status of a scheduled document.

Chapter 21: Creating a New Query

Figure 21-1: New Document Options
Figure 21-2: The Query Panel
Figure 21-3: Three sample hierarchies
Figure 21-4: Predefined conditions are special universe objects that apply complex conditions with one mouse click.
Figure 21-5: Using the same prompt in multiple data providers allows you to specify the same condition for each query.
Figure 21-6: Query Options
Figure 21-7: OLAP Panel for MS Analysis Services, Sales cube
Figure 21-8: Properties of Customer Dimension
Figure 21-9: Family selections for a particular member
Figure 21-10: The Essbase OLAP Panel
Figure 21-11: Refine filters with the Add/Remove Panel

Chapter 22: Complex Queries

Figure 22-1: Sample reports built by multipass SQL
Figure 22-2: One query generates two SQL statements. Select1 has an extra GROUP BY dimension.
Figure 22-3: Data Manager allows you to link common dimensions.
Figure 22-4: One table created with two data providers, with manually linked dimensions
Figure 22-5: Sets of criteria and how they intersect
Figure 22-6: Combined queries use UNION, INTERSECT, or MINUS operators.
Figure 22-7: A subquery selects conditions based on the results of another query.
Figure 22-8: Sample wine data for a calculation subquery
Figure 22-9: A user-defined object

Chapter 23: WebIntelligence

Figure 23-1: Customized InfoView start page
Figure 23-2: My InfoView allows you to customize the contents for multiple blocks.
Figure 23-3: Document list options
Figure 23-4: Options to Create and Edit Documents
Figure 23-5: BusinessObjects document viewed in HTML format
Figure 23-6: BusinessObjects document viewed in Enhanced document format
Figure 23-7: BusinessObjects document viewed in PDF format
Figure 23-8: Universe display options
Figure 23-9: Search for documents
Figure 23-10: WebI report
Figure 23-11: Popular block types
Figure 23-12: InfoView Drill mode
Figure 23-13: Refresh a query with prompts
Figure 23-14: Web Panel to create WebI documents
Figure 23-15: Query conditions and document filters
Figure 23-16: Sorts, breaks and calculations
Figure 23-17: Document settings
Figure 23-18: WebI OLAP Report

Chapter 24: WebIntelligence Version 6.0

Figure 24-1: InfoView home page
Figure 24-2: View options
Figure 24-3: Corporate Document list
Figure 24-4: Document Properties
Figure 24-5: Viewing a multiblock, multireport document
Figure 24-6: Prompts to refresh a query
Figure 24-7: Long lists of values are chunked.
Figure 24-8: Java Report Panel, Edit Query
Figure 24-9: The Filter Editor
Figure 24-10: Prompt options
Figure 24-11: Report page of the Java Report Panel
Figure 24-12: HTML Report Panel, Edit Query



 < Day Day Up > 



Business Objects(c) The Complete Reference
Cisco Field Manual: Catalyst Switch Configuration
ISBN: 72262656
EAN: 2147483647
Year: 2005
Pages: 206

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net