Universal Drill Through Service Guide

Universal Drill Through Service Windows

2

Universal Drill Through Service Guide

Copyright

Copyright © 2004 Business Objects. All rights reserved. If you find any problems with this documentation, please report them to Business Objects in writing at documentation@businessobjects.com.

Trademarks

Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. Contains ICU libraries (c) 1995-2003 International Business Machines Corporation and others. All rights reserved.

Use restrictions

This software and documentation is commercial computer software under Federal Acquisition regulations, and is provided only under the Restricted Rights of the Federal Acquisition Regulations applicable to commercial computer software provided at private expense. The use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in subdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at 252.2277013. Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352. 372-10-610-01

Patents

Part Number

Universal Drill Through Service Guide

3

Contents

Preface

Maximizing Your Information Resources

7

Information resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Chapter 1 About Drill Through 15

What does the administrator do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 What does the administrator need to know? . . . . . . . . . . . . . . . . . . . . . . . . 19 What is drill through? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Setting up drill through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Chapter 2 Drill Through Requirements 29

Normalized relational databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Star schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 What is a Business Objects universe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 How cubes and universes relate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Chapter 3 Designing the Target Universe 41

Designing the target database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Designing a star schema database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Creating the target universe from the database . . . . . . . . . . . . . . . . . . . . . . 46

Contents

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Working with existing translation maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Making translation maps available to WebIntelligence . . . . . . . . . . . . . . . . . . . . . . . . . . 49 What are translation maps? . . . . . . . . . . . . 92 Problems caused by outdated translation maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Building translation maps using UDS Designer . . . . . . . 50 Mapping from cubes to universes . . . . . . . . . . . . . . . . . . . . . . . . . 93 Source cube and target cube/universe locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Drill through workflow . . . 91 Changes that require updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Creating a translation map . . . 94 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Chapter 5 WebIntelligence in Drill Through 79 Creating WebIntelligence target reports . . . . . . . . . . . . . . . . 82 Chapter 6 Managing and Maintaining a Drill Through Environment 89 Why maintenance is necessary . . . . . . . . . . . . . . . . . . . . . . . . .4 Universal Drill Through Service Guide Chapter 4 Building Translation Maps 47 What is UDS Designer? . . . . 54 Importing data sources . . . . . . . . . . .

. . . . 86 Selecting member labels at the same level . .Universal Drill Through Service Guide 5 Examples What are the unit sales of different brands of soccer cleats in 2001 Q1 ? . . . . . . . . . . . . . . . . . . . . 86 Selecting member labels from different dimensions . . . . . . . . . . . . . . . . . . . . 87 Selecting member labels from the same and different dimensions . . . 87 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Selecting multiple measure cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Selecting member labels and values . . .

6 Universal Drill Through Service Guide Examples .

Maximizing Your Information Resources preface .

Packed with in-depth technical information. and consulting requirements. Business Objects also offers a complete range of support and services to help maximize the return on your business intelligence investment. and solutions The Business Objects business intelligence solution is supported by thousands of pages of documentation. business examples. on the Internet. available from the products. on CD. Maximizing Your Information Resources . services. education.8 Universal Drill Through Service Guide Overview Information. this comprehensive documentation set provides concrete solutions to your business problems. and by extensive online help systems and multimedia. See in the following sections how Business Objects can help you plan for and successfully meet your specific technical support. and advice on troubleshooting and best practices.

from where. Documentation on the web The full electronic documentation set is available to customers with a valid maintenance agreement on the Online Customer Support (OCS) website at www. View or download the Business Objects Documentation Roadmap at www. Online help. plus tips.businessobjects. This CD brings together the full set of documentation.htm Search the Documentation CD Search across the entire documentation set on the Business Objects Documentation CD shipped with our products. from the Business Objects Documentation Supply Store. we can help you quickly access the documentation and other information you need.com/services/documentation. or from your local sales office. and demo materials. Order the Documentation CD online. there is a summary of useful web addresses on page 12.htm Documentation from the products You can access electronic documentation at any time from the product you are using. Documentation Roadmap The Documentation Roadmap references all Business Objects guides and multimedia.businessobjects. Where do I start? Below are a few suggested starting points. or from the online Business Objects Documentation Supply Store at www.com/services/support.businessobjects. multimedia tutorials.com/services/documentation.htm Buy printed documentation You can order printed documentation through your local sales office. and guides in Adobe PDF format are available from the product Help menus. and lets you see at a glance what information is available.Universal Drill Through Service Guide 9 Information resources Whatever your Business Objects profile. and in what format. Information resources . multimedia. tricks.

and we will do our best to ensure that your suggestion is included in the next release of our documentation: documentation@businessobjects. Regularly check the sites listed below for the latest documentation. this is a regularly updated source of creative solutions to any number of business questions. you can get the latest documentation – in seven languages – on the Online Customer Support (OCS) website.com NOTE If your issue concerns a Business Objects product and not the documentation.com/services/support. www. How can I get the most recent documentation? You can get our most up-to-date documentation via the web.businessobjects.htm Maximizing Your Information Resources . from our desktop to our web solution? Try one of our multimedia quick tours or Getting Started tutorials. You can even contribute by sending us your own tips. For information about Customer Support visit: www. With a valid maintenance agreement. All are available via the Online Customer Support (OCS) website or on the Documentation CD. samples. Send us your feedback Do you have a suggestion on how we can improve our documentation? Is there something you particularly like or have found useful? Drop us a line. please contact our Customer Support experts.asp Product documentation We regularly update and expand our documentation and multimedia offerings.com/forms/tipsandtricks_login. Developer Suite Online Developer Suite Online provides documentation. and tips.businessobjects. for example.10 Universal Drill Through Service Guide Multimedia Are you new to Business Objects? Are you upgrading from a previous release or expanding. samples. Tips & Tricks Open to everyone. and tips to those customers with a valid maintenance agreement and a Developer Suite license via the Online Customer Support (OCS) website.

update. in connectivities.com/services/support.htm Services . or contact us at: www. we can offer a training package to suit your learning needs and preferred learning style. contact your local sales office.com/services/education. Australia Online Customer Support Our Customer Support website is open to all direct customers with a current maintenance agreement. and consulting to ensure maximum business intelligence benefit to your business.businessobjects. You can log. and provides the most up-to-date Business Objects product and technical information. Japan and Sydney.com/services/consulting. For more information. United Kingdom • Asia: Tokyo.businessobjects.businessobjects. contact Worldwide Customer Support at: www. and track cases from this site using the Business Objects Knowledge Base. Georgia • Europe: Maidenhead.htm Looking for the best deployment solution for your company? Business Objects consultants can accompany you from the initial analysis stage to the delivery of your deployment project. We operate three global customer support centers: • Americas: San Jose. Find more information on the Business Objects Education website: www. California and Atlanta.Universal Drill Through Service Guide 11 Services A global network of Business Objects technology experts provides customer support. How we can support you? Business Objects offers customer support plans to best suit the size and requirements of your deployment. and more. Expertise is available in relational and multidimensional databases. database design tools. education. customized embedding technology. Having an issue with the product? Have you exhausted the troubleshooting resources at your disposal and still not found a solution to a specific issue? For support in deploying Business Objects products.htm Looking for training options? From traditional classroom learning to targeted e-learning seminars.

Provides all the documentation. www. click the Knowledge Exchange link.businessobjects.com/services/ support.businessobjects. The latest Business Objects product documentation. documents.com Developer Suite Online www. Links to Online Customer Support.businessobjects. Technical articles. case resolutions.businessobjects. to download or view online.12 Universal Drill Through Service Guide Useful addresses at a glance Address Business Objects Documentation www.com Product documentation www. Business Objects product information Information about the full range of Business Objects products.htm Feedback or questions about documentation. kits and tips.com/services/ documentation. Tips & Tricks. Also.com Available to customers with a valid maintenance agreement and a Developer Suite license via the Online Customer Support (OCS) website. latest samples.businessobjects.techsupport. Practical business-focused examples. Documentation Roadmap. Business Objects Documentation mailbox documentation@businessobjects.com/forms/ tipsandtricks_login. From the Knowledge Base.asp Maximizing Your Information Resources .com Knowledge Base (KB) www.businessobjects.htm Content Overview of Business Objects documentation. use the Knowledge Exchange to learn what challenges other users – both customers and employees – face and what strategies they find to address complex issues.techsupport. Tips & Tricks www. Documentation mailbox. Documentation Supply Store.

www.businessobjects.com/services Business Objects Education Services www.htm Business Objects Consulting Services Information on how Business Objects can help maximize your business intelligence investment.com/services/ education.businessobjects.techsupport. Information about registering with Worldwide Customer Support. www.com/services/ consulting.businessobjects. resolving issues.businessobjects. The range of Business Objects training options and modules.Universal Drill Through Service Guide 13 Address Online Customer Support www.com Content Starting point for answering questions.htm Useful addresses at a glance .

scripts. directories. Maximizing Your Information Resources . This font is also used for all paths. Convention This font Indicates Code. the symbol ( ) indicates that the next line should be entered continuously with no carriage return. Some code more code $DIRECTORYPATHNAME The path to a directory in the Business Objects installation/configuration directory structure. Audience This guide is intended for administrators who need to set up drill through between WebIntelligence reports. For example: • $INSTALLDIR refers to the Business Objects installation directory.14 Universal Drill Through Service Guide About this guide This guide describes the Universal Drill Through Service and associated tool. SQL syntax. UDS Designer. computer programs. Placed at the end of a line of code. • $LOCDATADIR refers to a subdirectory of the BusinessObjects installation directory called locData. commands and files for UNIX. Conventions used in this guide The conventions used in this guide are described in the table below. For example: @Select(Country\Country Id).

About Drill Through chapter .

and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill down data. users can seamlessly carry over their data analysis from report to report. reporting and analysis within the same framework. UDS ‘remembers’ the point at which the user left the cube and carries this context across to the target WebIntelligence report.16 Universal Drill Through Guide Overview Universal Drill Through Service (UDS) is a technology that allows users to drill down into a WebIntelligence Relational report. you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the different contexts at which the user might drill through from report to report. As administrator. With UDS. UDS allows users to move from navigation of summarized OLAP cubes to more detailed query. Users can perform dynamic multidimensional cube analysis and access lower level details stored in the target report. or another WebIntelligence OLAP report. from a WebIntelligence OLAP report. About Drill Through . The user selects the cell or cells in the OLAP cube for drilling.

In this case.Universal Drill Through Guide 17 What does the administrator do? As the UDS Administrator.or snowflake-schema database that will consolidate all the data needed by the universe-based reports.or snowflake-schema database then you will not need to design a database specifically for drill through. Create a translation map A translation map is an XML file that tells the Drill Through Service how to translate the context from the source to the target report when the user drills through. • Migrate data from RDBMSs and/or flat files into this database. you will use the existing database. However. you could use any XML editing tool to create one. a specialized XML tool designed specifically for building translation maps.or snowflake-schema database If your source cube is already based on a star. Design a universe for target user reports If your users are drilling from OLAP cubes to universe-based relational reports. Design a star. • Design a universe for target user reports. hierarchies and members in the cube in all contexts at which the user will be able to drill through from the cube. Because maps are XML. you are much more likely to use UDS Designer. You need to carry out some or all of the following tasks to ensure this seamlessness: • Design a star. • Create a translation map using UDS Designer that tells the Drill Through Service how to translate the context from the OLAP cube to the universe on which the WebIntelligence Relation target reports are based. • Build target reports built against the target universe. you need to design a WebIntelligence universe whose structure maps to the structure of the source cube. The universe must contain objects that correspond to the levels. You build a map by assigning objects to a hierarchical map model and setting various properties associated with these objects. What does the administrator do? . it is your job to ensure that drill through is seamless for the user. and you will also have no need for data migration.

About Drill Through . The Drill Through Service opens these reports automatically when the user chooses to drill through from a context specified in a translation map. Target reports provide data at a more detailed level than the data available in summarized and aggregated OLAP cubes.18 Universal Drill Through Guide Design target reports You build WebIntelligence target reports against the target universe or OLAP cube that contains detailed data.

see the Hyperion Integration Server Desktop OLAP Model User’s Guide. For information on star or snowflake schema databases and data warehouses. 1998). For creating universe-based WebIntelligence reports. 1996) and The Data Warehouse Lifecycle Toolkit: Tools and Techniques for Designing. see the BusinessObjects Designer’s Guide. The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses (John Wiley & Sons. For creating OLAP cubes using Hyperion Integration Server. What does the administrator need to know? . Developing. see the Getting Started with WebIntelligence guide. You should have experience in most or all of the following areas. see Ralph Kimball. you need a wide range of knowledge and experience to set up a UDS environment. and Deploying Data Warehouses (John Wiley & Sons.Universal Drill Through Guide 19 What does the administrator need to know? As the large number of different tasks in the previous section indicates. For designing and building BusinessObjects universes. depending on the environment in which you are setting up drill through: • Advanced SQL • Designing star or snowflake database schemas • Data migration • OLAP cubes • Creating OLAP cubes • Designing and building BusinessObjects universes • Creating universe-based WebIntelligence reports You can get further information from the following sources.

When the user drills on value cells. Navigate the data to arrive at the same ‘context’ reached in the first data source. drill through includes the dimension members from the row and column axes that intersect at the cell(s). Continue data analysis using the new query tool. drill through also includes members from dimensions on the filter axis. data is stored in numerous sources. Without drill through. or a dimension member or members. drill through includes only that member(s). this is a tedious and time-consuming task. A user can drill through from a value cell or cells. In both cases. the target cube could be: • a different cube in a different database • adifferent cube in the same database • the same cube When the user drills through from source to target. On reaching the limit of the data in one source. Start the query tool used to access this data. Identify the data source containing the data necessary for further analysis. but it is often necessary to access more than one source when analyzing this data. 4.20 Universal Drill Through Guide What is drill through? Drill through provides integration between data sources that contain related but different data stored in different data sources. About Drill Through . the analyst needs to do the following: 1. The scenarios that drill through currently supports are: Source Microsoft and Essbase/DB2 OLAP Target Relational (BusinessObjects universes) Microsoft and Essbase/DB2 OLAP This means that the following general drill through scenarios are possible: • OLAP to relational (BusinessObjects universe) • OLAP to OLAP In the OLAP to OLAP scenario. 3. drill through carries the context of the source report to the target report. 2. Drill through provides integration between data sources that contain related but different data. In most enterprises. When the user drills on member(s).

4. Load the appropriate universe containing data down to the level of unit sales of cleats by quarter. he must: 1. Drill through components The following sections describe the components that make up drill through. Using the cube. 3. he now wishes to investigate further the sales of individual brands of cleat by quarter. Create a report showing sales of soccer cleats by quarter for the year 2001. Even though this data is not in the cube. the analyst simply elects to drill-down into the data showing unit sales of brands by quarter. shoe. To do this. golf shoes. With drill through. While browsing the data in the OLAP cube. this complex process becomes straightforward. Drill down into this data to analyze sales figure by quarter by brand. OLAP target cube The target cube contains data at a lower level of detail. However. uniform etc. and passes the analyst’s ‘context’ in the OLAP cube to this report. OLAP source cube The source cube contains data at an aggregated level. What is drill through? . Universal Drill Through Service Universal Drill Through Service is the name for the technology that translates a user’s context in a source report to a target report. the analyst has drilled down as far as producing a report showing the sales of cleats by quarter. baseball uniforms) and a WebIntelligence universe that breaks down sales by each different brand of cleat.Universal Drill Through Guide 21 EXAMPLE What are the unit sales of different brands of soccer cleats in 2001 Q1 ? In this example the data analyst needs to work with two data sources: an OLAP cube that provides unit sales data down to the level of the type of sports equipment (soccer cleats. The analyst can then continue drilling into the data in the WebIntelligence report. Universal Drill Through Service (UDS) opens the appropriate WebIntelligence report built against the appropriate universe. using the information provided in a UDS map (see the section UDS maps below). 2. Start WebIntelligence.

Drill through architecture It is possible to examine the drill through architecture from several angles: overall architecture.22 Universal Drill Through Guide UDS maps Maps are files that tell the Drill Through Service exactly how to carry the drill context from the source cube to the target universe (see Building Translation Maps on page 47). the target universe is a Business Objects universe built against the target database. You create UDS maps using UDS Designer (see below). Ideally. About Drill Through . A general rule of thumb is that each measure in the OLAP cube will require its own target report. This makes mapping OLAP cube members to universe objects simpler. this database should be configured in a star or snowflake schema. (see Designing the target database on page 43). see Drill through architecture on page 22. However. Target universe In an OLAP-to-Relational scenario. Each possible ‘context’ at which you wish to allow the analyst to drill through to the target universe must be covered by a target report (see Creating WebIntelligence target reports on page 81). Target reports Target reports are the WebIntelligence reports invoked by the Drill Through Service when the analyst drills outside the data contained in the source cube. the only hard criterion for target database design is that it must be possible to map the members in the OLAP cube to the objects in the target universe. For more details on how UDS maps fit into the overall drill through architecture. It must be configured to match the structure of the source cube (see Drill Through Requirements on page 29). the target database is the database on which the target universe is built. UDS Designer UDS Designer is the graphical tool used to build UDS maps (see Building Translation Maps on page 47). This is because the OLAP measures contain data at a summarized level. the report corresponding to each measure therefore provides more detailed data for that measure. WebIntelligence architecture and runtime architecture. Target database In an OLAP-to-relational scenario.

Universal Drill Through Guide 23 Overall drill through architecture The following diagram illustrates the relationships between the different components of drill through: Drill through implementation in WebIntelligence The following diagram illustrates the relationships between the different components of drill through as implemented in WebIntelligence: What is drill through? .

This highlights the two data packages that the Drill Through Service uses: the drilled data package and the translation map: Why drill through was difficult before Until recently. time-consuming and maintenance-heavy. As a result. meaning that the dimensions and levels in an OLAP cube would be unlikely to map to a relational data source within the same enterprise. Thus. a single drill through model was not feasible as it would need to account for the metadata models of all the supported source and target data sources. drill through has thus far existed in two niches only: complex. About Drill Through . different vendors’ OLAP and relational solutions differ considerably in their metadata models.24 Universal Drill Through Guide Run time architecture The following diagram shows the run time implementation of the drill through architecture. because the source and target data sources do not share similar metadata. Proprietary solutions solve the problem of incompatible metadata at the cost of supporting drill through from the vendor’s cubes only to the vendor’s relational source only. In this situation. custombuilt drill through solutions. Furthermore. databases across an enterprise were rarely synchronized. or proprietary drill through solutions provided by vendors. drill through is extremely complex.

OLAP object model WebIntelligence uses a universal OLAP object model to access OLAP cubes hosted on many different OLAP servers. database designers recognize the need to synchronize data sources across an enterprise. The universe translates user queries into SQL.the BusinessObjects OLAP model and the BusinessObjects relational model (universe). shielding the user from the often complex database-specific structures in which data about these objects are stored. and the object model handles the complexity of translating user actions into MDX.provides a layer of abstraction between WebIntelligence and relational data sources in the same way that the OLAP model insulates WebIntelligence from the OLAP cube. By placing this layer of abstraction between the OLAP server and the client tool. Because the hierarchical nature of a WebIntelligence universe closely resembles the structure of an OLAP cube. This greatly simplifies communication between OLAP-OLAP or OLAP-relational data sources because drill through needs to deal with at most two metadata models .or snowflake-schema relational source.Universal Drill Through Guide 25 Why drill through is possible now Today. Business Objects universe A universe .Business Objects’ patented ’semantic layer’ . This is essential if drill through is not to be prohibitively complex. they are now basing OLAP cubes on relational data sources. What is drill through? . How Business Objects enables drill through With WebIntelligence. If a cube is built from a star. both the cube and the relational database share similar metadata. It sees cubes hosted on different OLAP servers through the same object model. WebIntelligence removes the complexity from querying OLAP cubes. drill through is a good-fit technology for WebIntelligence. In particular. the query language understood by OLAP servers. The universe abstracts the database structure into a set of hierarchically-organized objects that represent the real-world objects about which the database stores data. Business Objects has both a standard OLAP model and a standard model for accessing relational data (the BusinessObjects universe).

About Drill Through . see What is a Business Objects universe? on page 34.26 Universal Drill Through Guide NOTE For more information on universes.

Example drill through environment WebIntelligence comes with a comprehensive set of materials to demonstrate a Drill Through environment.Universal Drill Through Guide 27 Setting up drill through In order to set up a Drill Through environment you need to carry out the steps described in What does the administrator do? on page 17. These are: • Source cubes • Source report (OLAP Drill-Through Report) • Target universe database (MS Access) • Target universe (Retail2002) • Target Report (MonthCustNameProdDepSales) • Target report This manual will refer to this material for all examples and demonstrations. Setting up drill through .

28 Universal Drill Through Guide About Drill Through .

Drill Through Requirements chapter .

and the database should be in a star schema to facilitate the universe design. For OLAP-to-OLAP drill through: OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill through. Drill Through Requirements .30 Universal Drill Through Guide Overview This chapter looks at the design requirements for a successful drill through environment. For example. the design of the universe on which the target reports are built needs to mirror the design of the source OLAP cube. each component must be designed according to specific guidelines. if you are using OLAP-relational drill through. The rest of this chapter examines the issues surrounding relational databases in OLAP-to-relational drill through. except that the target universe objects are replaced by target OLAP levels. For Drill Through to function correctly. The design requirements for a drill through environment are as follows: For OLAP-relational drill through: • The target relational database is ideally in a ’denormalized’ a star or snowflake schema. (The following sections describe the differences between normalized and star schema databases. although any schema that supports mapping to the OLAP cube is workable. and the designs of the various components are interrelated.) • The classes and objects in the target universe map to the levels and dimensions in the source OLAP cube.

while the later rules deal with the abstract. Codd’s earlier rules deal with tangible things. collectively these rules are referred to as normalization rules. database researcher E. A normalized relational database is ideal for data input. like relationships or events. In a correctly-normalized database. Because the data has been normalized into many tables. each table stores data about one thing and one thing only. a complex query might require data from a large number of tables. or more abstract. Normalization is designed to eliminate data rendundancy (the storing of the same piece of data in more than one place in a database) and therefore reduce the risk of errors when writing to and reading from a database. the retrieval of data from such a database is often slow. The ‘things’ in question might be tangible. Normalized databases are usually found in On-Line Transaction Processing (OLTP) systems. the primary purpose of which is data entry.Universal Drill Through Guide 31 Normalized relational databases In 1970. Normalized relational databases . like employees or departments. This process of joining the data from different tables in order to present a query result is an intensive database operation. Further researchers added additional rules. However. Codd formulated a series of rules for the design of relational databases.F. Car rental reservation systems or Point of Sale (POS) systems are examples of OLTP.

A Product dimension table containing all this data is a good example of the kind of highly denormalized table found in star schemas. The fact table contains numeric data with which you can measure business performance: for example. Fact tables. As you move down through the hierarchy. these three distinct ‘things’ would probably be stored in three tables. dimension tables and hierarchies A star schema consists of a central ‘fact’ table. Snowflake schemas are less common because the database space saved by normalization is small (in a large star schema database. Star schema databases are populated from OLTP databases. Snowflake schemas A snowflake schema is similar to a star schema except that the hierarchies in the dimension table are ‘normalized out’ to some extent. For example. Star schemas violate normalization rules spectacularly. As a general rule. Dimensions usually contain hierarchies. customer and time period. The OLTP data is transformed to fit into the star schema. In a normalized structure. and the database is refreshed periodically from the OLTP systems. A star schema almost always includes a table or tables that store time data. and the joining of the snowflaked tables Drill Through Requirements . As a result. The star schema maps closely to the structure of an OLAP cube. In this case it would be possible to examine unit sales by product. a database might contain Time. For example. joined to numerous ‘dimension’ tables which radiate around it. data in OLAP cubes is often drawn from data warehouse databases designed as star schemas. they are used strictly for reporting rather than data input.32 Universal Drill Through Guide Star schemas The star schema is an alternative database design that is optimized for data output. Product and Customer dimensions linking to a fact table storing unit sales. because the primary purpose of such databases is to allow for the analysis of trends over time. Dimension tables join to the fact table and relate these measures to different aspects of the business. approximately 95% of the space is occupied by the fact table). a Product dimension might contain hierarchy levels such as Product Category. but they also speed up data retrieval by a significant degree. numbers of products sold. its data becomes progressively more specific. Product Subcategory and Brand Name.

Universal Drill Through Guide 33 adds additional overhead. The example database is predominantly in a star schema. Star schemas . although the Product dimension is ‘snowflaked’ into the PRODUCT and PRODUCT_CLASS tables.

Universes insulate users from the complexities of SQL and relational data structures by presenting the data in terms familiar with the user.34 Universal Drill Through Guide What is a Business Objects universe? Universes are Business Objects’ patented ’semantic layer’ that sits between the BusinessObjects client tool and its relational data source. Drill Through Requirements . The hierarchical organization of data in universes is very similar to the organization of data in an OLAP cube. which makes mapping between the two data sources possible.

although any schema that allows mapping of cube members to universe objects is workable. universe and database in the demonstration material more closely. the database should be in a star or snowflake schema. In level translation a dimension level is mapped to a universe object where all the members for a dimension level map to a universe object and the member name corresponds exactly to the universe object value (eg. and the Unit Sales measure. To find this information in an OLAP cube. Relational database Ideally.Universal Drill Through Guide 35 How cubes and universes relate OLAP cubes and Business Objects universes are both hierarchical structures that are used to identify specific pieces of numerical data. 2000Q1 = 2000Q1) Design requirements The following sections examine the structures of the cube. in order to demonstrate the structure of the components in a drill through environment. the Soccer Cleats object within the Product class. the Product Dimension in order to find Cleats. To do the same information in a WebIntelligence universe. and the Accounts dimension in order to find the unit sales. for example the number of soccer cleats sold in California in Q2 2001. the analyst would navigate to the California object within the Customer class. The following figure shows the schema for the example MS Access database that How cubes and universes relate . Cube Term Dimension Level Cube Data ‘Product’ Universe Term Universe Data Class ‘Product’ ‘Brand Name’ ‘Brand Name’ Object (dimension or detail) ‘Cleats’ Value Member ‘Cleats’ The basic type OLAP-relational mapping provided by UDS is "level translation”. the analyst would explore the Customer dimension in order to find California. The classes and objects in universes therefore map to the dimensions and hierarchy levels in an OLAP cube.

A composite name is built from the member name qualified by the names of parent members. a Time dimension containing data for multiple years cannot contain multiple members called ‘March’. For example. For example. the month is qualified by both the quarter and the year in order to make the member name unique. the member ‘March’ in the year 2001 could be named ‘2001Q103’.36 Universal Drill Through Guide ships with WebIntelligence. you need to account for the fact that members in Essbase/DB2 OLAP cubes must be unique throughout the entire cube. although the Product dimension is ‘snowflaked’ into the PRODUCT and PRODUCT_CLASS tables. Drill Through Requirements . In this case. You solve this by creating a composite name for such members. Making member names unique When building your database. This database is predominantly in a star schema.

However. ’SportsWear’ is a member in the cube level and a value of the universe object. How cubes and universes relate . See the next section. Open the map using UDS Designer (see the chapter Building Translation Maps on page 47 for instructions on using this tool). Universe The classes. levels and measures in the source cube. and ess_quarter (in the form ‘20001Q1’) to uniquely identify the quarter. The translation map maps the cube level Product Family to the universe class/object Product/Product Family. the TIME_PERIOD table contains the columns ess_month (in the form ‘2001Q103’) to uniquely identify the month. NOTE You can also solve the problem of unique member names at the universe level. The table below shows example mappings from the demo universe and cube shipped with WebIntelligence. Cube Dimension Level Member Product Product Family Sportswear Class Object Value Universe Product Product Family Sportswear You can see this mapping by examining the demonstration translation map supplied with WebIntelligence.Universal Drill Through Guide 37 You need to account for this when designing your database. the universe can contain additional items not in the source cube. objects and measures in the universe must match the dimensions. In the example database.

38 Universal Drill Through Guide Designing for unique members If your source cube is an Essbase/DB2 OLAP cube. In Essbase/DB2 OLAP. For example. Cube designers solve this by qualifying member names with the names of one or more parent members. Because universes provide a layer of abstraction between the database and the user. This is what the object definition would look like in Designer: Drill Through Requirements . Creating universe objects to map to unique members You can create universe objects that map to the unique members in a cube. the names of the months in the year must be qualified with the year to make them unique. The time dimension members are often named in this way. you could create a universe object called Essbase Quarter that concatenates the quarter’s parent year followed by the quarter. it needs a name like ’2001March’. each member name must be unique throughout the entire cube. the March 2001 member cannot be named ’March’. you can add objects to the universe that derive from various objects in the database. you will need to take the cube’s unique member names into account. If the time dimension contains data for more than one year. For example. in the form "2000Q1".

other than the normal restrictions imposed by Essbase/DB2 OLAP (for example. as described in the previous sections. The cube design carries over to the design of the universe and target databases and places restrictions on those components.Universal Drill Through Guide 39 Cube There are no restrictions on cube design. How cubes and universes relate . the need to have unique member names).

40 Universal Drill Through Guide Drill Through Requirements .

Designing the Target Universe chapter .

42

Universal Drill Through Guide

Overview
This chapter describes the WebIntelligence target universes on which you base your drill through target reports in OLAP-to-Relational drill through.

Designing the Target Universe

Universal Drill Through Guide

43

Designing the target database
If you are basing your target universe on the same database that populates your source cube, you do not need to design a target and populate a target database. If you are designing a new database for your target universe, you must be aware that, for the OLAP dimensions that you wish the user to be able to drill through from, the target universe needs to map exactly to the structure of the OLAP cube. The ideal design for the underlying database for this universe is a star or snowflake schema. These schemas map closely to OLAP cubes (and are often used to feed data to cubes in OLAP databases); as a result, such a schema is also ideal for a universe that maps to the structure of an OLAP cube.
NOTE

The target database does not need to map to the structure of the whole source cube, just to those dimensions that you wish users to be able to drill through from. After you have designed your database, you will need to populate it. How you do this depends on factors such as the operating system and RDBMS on which the database is hosted. If you use views in the target database, you do not need to perform as much data migration.

Designing the target database

44

Universal Drill Through Guide

Designing a star schema database
In a star schema, the numeric data (the Accounts dimension in an Essbase/DB2 OLAP cube) is stored in a central ‘fact’ table. The dimension tables (equivalent to the dimensions in an OLAP cube) radiate around this fact table and are joined to it via foreign keys. (See Designing a star schema database on page 44 for more details.) The example drill through database supplied with UDS Designer is arranged almost entirely in a star schema, although the Product dimension has been split (or ‘snowflaked’) into the PRODUCT and PRODUCT_CLASS tables. Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases.

Essbase/DB2 member naming restrictions
In an Essbase/DB2 OLAP cube, each member name must be unique throughout the entire cube. Essbase/DB2 OLAP cube designers typically work around this restriction by qualifying the name of the member with the names of its parent members. For example, it is not possible to have a member called ‘Q2’ if the cube contains data for more than one Q2 (which is likely). In this situation, the cube designer could qualify the name of the quarter with the name of the year in order to make the member name unique. The member name for Q2 of 2001 would be 2001Q2. You can account for this in the database by adding additional columns where necessary to allow for mapping to uniquely named-members. You can see this in the TIME_PERIOD table of the example database, which contains the columns ess_quarter (uniquely-named quarters) as ess_month (uniquely-named months).
NOTE

You can also account for unique members at the universe level. See Creating universe objects to map to unique members on page 38 for more details.

The Accounts dimension
An Essbase/DB2 Accounts dimension might contain data that is not in the relational data source. The Accounts dimension can contain aggregates, while the relational data might contain the lowest-level numerical data only. In this scenario it is not possible to map the Accounts dimension to the database.

Designing the Target Universe

To do this.Universal Drill Through Guide 45 This should not present an issue as the mapping of an Accounts dimension is rarely useful. Designing a star schema database .in itself it is not relevant to drill through context. Drill Through needs to map dimensions and levels between the cube and database. Numerical data is retrieved based on the dimensions and levels that the user is querying . The purpose of Drill Through is to allow the user to retrieve lowerlevel numerical data from the database than is available in the cube.

Cube Term Dimension Level Cube Data ‘Product’ Universe Term Universe Data Class ‘Product’ ‘Brand Name’ ‘Brand Name’ Object (dimension or detail) ‘Cleats’ Value Member ‘Cleats’ Designing the Target Universe . the objects must map to the levels. The following table shows some example correspondances between the example cube and universe shipped with WebIntelligence.46 Universal Drill Through Guide Creating the target universe from the database In the target universe. and the values of those objects must map to the cube members. the classes must map to the dimension in the OLAP cube.

Building Translation Maps chapter .

Drill through currently supports Microsoft SQL Analysis Services and Essbase/DB2 OLAP as OLAP sources. Building Translation Maps .48 Universal Drill Through Guide Overview This chapter describes UDS translation maps and how to build them using UDS Designer. Translation maps tell the Drill Through Service how to translate the context from an OLAP source cube to a universe (OLAP-to-relational drill through) or OLAP target cube (OLAP-to-OLAP drill through).

UDS Designer is a specialized XML editor specifically tailored to building maps. you can build translation maps with any XML editing tool.exe. What is UDS Designer? .Universal Drill Through Guide 49 What is UDS Designer? UDS Designer is a graphical tool that you use to build translation maps. UDS Designer is installed by default in the <BO_Install_Folder>\Business Objects Enterprise 6\bin folder with a Desktop or Server installation of the BusinessObjects suite . The application file name is uds_designer. However. Translation maps are XML files.

• Target OLAP level . Member translations You use member translations to exclude specific members that you do not want to be translated as part of a level translation. the dynamic time series members in an Essbase cube (Quarter to Date) have no equivalent in a relational database. It has the following components: • Target universe class . • Parent translation .a rule that specifies how to manipulate the member when passing it from the source to the target. It describes how the values in the cube relate to the values in the report. the OLAP level that an OLAP member translates to. you assign a member translation to it and disable translation for the member. hierarchies and levels. For example.an additional translation rule used to qualify the member with its parent member or members where the name of the member alone is not enough to uniquely identify it in the universe. There are two basic translations possible within a map: level translations and member translations. • Target universe objects .in an OLAP to OLAP translation. the universe class that an OLAP member translates to. and what their equivalents are in the target data source. Because the originating data sources are OLAP cubes. Building Translation Maps .50 Universal Drill Through Guide What are translation maps? A translation map is an XML file (with the extension UDM) that tells the Drill Through Service how to translate the context from the source cube to the target WebIntelligence report (which can be based on a universe or an OLAP cube) when the user drills on a cell or cells. You build a translation map by specifying which structures in the originating data source you want to translate. this means that the map is structured like a cube: it consists of dimensions. • Translation rule . To prevent this member from being translated. the universe objects that an OLAP member translates to.in an OLAP to relational translation.in an OLAP to relational translation. Level translations A level translation is a general rule that applies to all members at a particular level in an OLAP cube.

Universal Drill Through Guide 51 What is in a translation map? A translation map contains the following information: • Details of the originating data source (OLAP cube) • Details of the target data source (WebIntelligence report) • Details of each dimension and its associated hierarchies and levels and whether these are enabled for drill through • The level and member translations associated with the levels. Importing the source cube on page 56 Importing the target universe on page 58 Import the target universe OR Import the target cube Importing the target cube on page 59 Specifying member translations on page 67 Add the translations to the map Specify the target reports Adds the Specifying target reports WebIntelligence target on page 73 reports to the translation map What are translation maps? . • The target reports based on the target cube or universe.. you do the following: Step Import the source cube Description Loads the source cube metadata into UDS Designer Loads the target universe metadata into UDS Designer Loads the target cube metadata into UDS Designer Adds the translations that describe the cubeto-universe mapping to the translation map For further information. Workflow for building a translation map To build a translation map.. see.

You can then add these metadata objects to the translation map. hierarchies. you specify the target WebIntelligence reports to which the map applies. you make its metadata (classes and objects) available to UDS Designer for the same reason. Building Translation Maps . Add the translations to the map This is the key process in which you tell the Drill Through Service how to translate the context from the source cube to the target WebIntelligence report. You do this by adding translation objects to the map and setting their properties. Import the target universe When you load the target universe. you make its metadata available to UDS Designer. Specify WebIntelligence target reports After you have added all the translations to the map. you make its metadata (dimensions. These are the reports that the user will drill through to from the source OLAP cube. levels and members) available to UDS Designer. Import the target cube When you load the target cube.52 Universal Drill Through Guide Import the source cube When you load the source OLAP cube.

Mapping from cubes to universes . If a relational data source contains data for more than one year. the Customer dimension in the demonstration cube contains the City level.Universal Drill Through Guide 53 Mapping from cubes to universes Data is structured in universes in a design that is very similar to the structure of OLAP cubes. The simpler form is 1:1 mapping and the more complicated form is qualified 1:1 mapping. you need to use a Parent Translation object to qualify the name of the member with the name of its parent. For drill through to work. This maps to the Customer class in the demonstration universe. March 2001 and March 2002 will both be stored as ’March’. In simple 1:1 mapping there is no need to qualify the source member in the translation map because the target objects in the universe are unique and unambiguous. Qualified 1:1 mapping In qualified 1:1 mapping the target objects in the universe are not unique. Simple 1:1 mapping In simple 1:1 mapping. There are two flavors of structure mapping. The table below gives examples from the Rtl2002 cube and Rtl2002 universe supplied with the Drill Through Service. you must be able to map the structure of the source cube to the structure of the target universe. the cube members map exactly to equivalent objects in the WebIntelligence universe. Because a translation map must uniquely associate each cube member with a corresponding universe object. levels and members in the cube must correspond exactly to the classes. For example. This situation commonly occurs when translating members in the Time dimension. objects and values in the universe. the child objects of the year (for example the quarters and months) will not be unique in the database. objects and object values in a universe. which contains the City object. and one of the members of this level is ‘San Diego’. In order to map the source OLAP members to the target universe objects unambiguously. it is necessary to qualify the member with the name of one or more of its parent members. This simple mapping is known as structure mapping. One of the values of this object is ‘San Diego’. levels and members in a cube correspond to the classes. This means that the values of the dimensions. The dimensions.

54 Universal Drill Through Guide Building translation maps using UDS Designer This section describes how to build a UDS Map using UDS Designer.pane displays the translation map jects from the translation map The Properties area allows you to change the properties of the currently-selected object in the translation map Building Translation Maps . The UDS Designer main interface is shown below. hierarchies and levels in the source cube The Universe Target Information pane shows the classes and objects in the target universe The Mapping Parts pane contains the different objects that you can add to a translation map You use the Add and Delete The Map Model buttons to add or remove ob. The OLAP Source Information pane shows the dimensions.

Universal Drill Through Guide 55 Navigating translation maps You navigate a translation map in the Map Model pane. You select objects in this hierarchy and change their properties in the Properties area. Building translation maps using UDS Designer . the Properties area changes to display the properties that are relevant to that object. When you select an object. UDS Designer displays the map hierarchically in a tree format.

Select New from the File menu. 2.56 Universal Drill Through Guide Importing data sources Your first step in creating a translation map is to import the metadata from both the source cube and the target cube/universe. it is not possible to change the data sources. NOTE When working with a previously-saved translation map that you open using UDS Designer. Importing the source cube To import the source cube. Building Translation Maps . To do this you need to connect to both the OLAP database containing the cube and the WebIntelligence repository or OLAP database containing the universe/target cube. Click OLAP to Relational or OLAP to OLAP then click OK. do the following: 1. The Map Types dialog box appears.

levels and hierarchies in the source cube. 11. (This step does not apply to MS OLAP. If connection is successful. the DataBases dropdown list box is populated with names of the OLAP databases available on the server.Universal Drill Through Guide 57 The Olap Source Information dialog box appears. Select the cube that you want to connect to from the Cubes dropdown list box. 5. Select the database containing the cube you want to access from the Databases dropdown list box. Click Connect. The Cubes dropdown list box is populated with the names of all the cubes available in the database you selected. Importing data sources . Select the OLAP server type from the Server Type dropdown list. hierarchies and levels in the cube. The OLAP Source Information pane is populated with the dimensions. 7. 4. Enter the name of the OLAP server in the OLAP Server box. Click Load Cube. 10. 8.) 6. Enter your OLAP server username and password in the User Name and Password boxes. UDS Designer attempts to connect to the server using the information you have given. In addition. 9. 3. the translation map is populated with all the dimensions.

Select a universe from the Universes dropdown. then click Load Universe. UDS Designer populates the Universe Target Information with the classes and objects from the universe. hierarchies and levels to the translation map. the Choose Universe dialog box opens automatically after you have loaded the source cube. check that the repository database is available and that you have the correct middleware installed to access it. UDS Designer does not automatically assign all the dimensions. In this case. Building Translation Maps . you will see the Universe Target Information dialog box. Enter your User Name and Password and click OK. Importing the target universe If you selected OLAP to relational translation.58 Universal Drill Through Guide NOTE You can also import a source cube when you already have a translation map loaded. If you cannot connect to the repository. If the connection to the repository succeeds.

Universe security is governed entirely by the user ID used to connect to WebIntelligence.Universal Drill Through Guide 59 Importing the target cube If you selected OLAP to OLAP translation. The displayed cube members and values are based on the user ID used to connect to the OLAP cube. the OLAP Source Information dialog box appears again. You follow the procedure described above to connect to the source cube. Security Drill through security is handled entirely by the originating and target query tools. Importing data sources .

deleting. The Properties area changes to reflect the properties appropriate to the object you select. Building Translation Maps . Click the Add button to add the object to the translation map. You can then modify these properties. 3.60 Universal Drill Through Guide Creating a translation map Once you have loaded the source and target metadata you are ready to start building your translation map. You can add additional objects to be associated with an object in the translation map. do the following: 1. when you select an object in the Map Model pane. Select the object to be added in the OLAP Source Information. delete a dimension. replacing and enabling dimensions The Map Model pane shows dimensions hierarchically beneath the map object in the Map Model pane. These objects come from three sources: • The OLAP Source Information pane • The Universe Target Information pane • The Mapping Parts pane To add an object to the translation map. When you loaded the cube metadata. replace a dimension and enable/disable an existing dimension. You can perform four tasks relating to a dimensions: add a new dimension. 4. Use the Properties area to specify the properties of the added object. the Properties area on the right displays the properties of the selected object. Now. Universe Target Information or Mapping Parts panes. 2. UDS Designer automatically loaded all the cube dimensions. Select the object in the translation map. hierarchies and levels into the translation map. Adding.

Universal Drill Through Guide 61 . Creating a translation map .

Select the Map object in the Map Model pane.62 Universal Drill Through Guide Adding. Building Translation Maps . removing and replacing dimensions You can add. 2. Click Add. The dimension is added to the translation map. Select the dimension in the OLAP Source Information pane. remove or replace dimensions in the translation map. 3. To add a dimension: 1.

Click Remove. 2. You need to enable the dimensions that you wish to be translated. all dimensions are not enabled for translation.Universal Drill Through Guide 63 To remove a dimension: 1. Select the replacing dimension in the OLAP Source information pane. The dimension is removed from the translation map. To add a hierarchy: 1. NOTE To disable an enabled dimension. remove. Select the dimension to which you want to add a hierarchy in the Map Model Creating a translation map . Select Translation Enabled to enable translation for the dimension. replace and enable/disable hierarchies for translation in the translation map. Select the dimension to be replaced in the Map Model pane. The Properties area shows the dimension properties. 2. The dimension is replaced with the new dimension from the source cube. Adding. deleting. Initially. You can add. Enabling dimensions for translation When you load the source cube for a new translation map. Click the dimension in the Map Model pane. select Translation Enabled again. Select the dimension in the Map Model pane. 3. 2. Click Add. replacing and enabling hierarchies You work with hierarchies by selecting dimensions and hierarchies in the Map Model pane. UDS Designer adds all the cube dimensions to the translation map. To enable a dimension: 1. To replace a dimension: 1.

The hierarchy is replaced with the new hierarchy from the source cube. select Translation Enabled again. 2. NOTE To disable an enabled hierarchy. 2. Click Add. Select the hierarchy in the Map Model pane. Select the hierarchy in the OLAP Source Information pane. 3. To remove a hierarchy: 1. The hierarchy is added to the dimension in the translation map. Enabling hierarchies for translation To enable a hierarchy for translation: 1. Click Remove. The hierarchy is removed from the translation map. 3. Select Translation Enabled in the Properties area to enable translation for the hierarchy. The Properties area shows the hierarchy properties. 2. Building Translation Maps . Click the hierarchy in the Map Model pane. Select the replacing hierarchy in the OLAP Source information pane. Select the hierarchy to be updated in the Map Model pane.64 Universal Drill Through Guide pane. Click Add. To update a hierarchy: 1. 2.

remove or replace levels in the translation map. deleting. To add a level: 1. Creating a translation map . 2. Select the level in the OLAP Source Information pane. replacing and enabling levels You work with levels by selecting the levels in the Map Model pane. You can add.Universal Drill Through Guide 65 Adding. Select the dimension hierarchy to which you want to add a level in the Map Model pane.

Click Add. To update a level: 1. 2. To remove a level: 1. Building Translation Maps . The level is removed from the translation map. Select the level to be updated in the Map Model pane. The level is added to the dimension/hierarchy in the translation map. Click Remove. The level is replaced with the new level from the source cube. Click Add. 3.66 Universal Drill Through Guide 3. Select the replacing level in the OLAP Source Information pane. 2. Select the level in the Map Model pane.

Specifying member translations A level translation applies to all members at a level. Click the level in the Map Model pane. 3. Populating translation objects automatically UDS Designer can populate the class and object properties automatically when you add a level translation. Select the universe object in the Target Universe information pane. Creating a translation map .Universal Drill Through Guide 67 Enabling levels for translation To enable a level for translation: 1. do the following: 1. The Properties area shows the level properties. 2. you can do so by adding a member translation. the Universe Class and Universe Object properties of the level translation are automatically populated with the universe object’s parent class and object name respectively. Select the level in the Map Model pane. If you need to specify a translation for a particular member. select Translation Enabled again. NOTE To disable an enabled level. 2. To add a level translation and automatically populate these properties. Click Add. Select Translation Enabled to enable translation for the level. Because you specified a target universe object in step 2.

Select the member’s level in the Map Model pane. Select Member Translation in the Mapping Parts pane. Specify the class and object properties for the level translation.68 Universal Drill Through Guide To add a member translation: 1. Building Translation Maps . 3. UDS Designer adds a level translation (if one is not already present) and a member translation to the level. Click Add. 2. 4.

Select the Source Member Unique Name component of the member translation. Select the Target Unique Value component of the member translation in the Creating a translation map . Type the member name in the Member Unique Name box in the Properties area. 7.Universal Drill Through Guide 69 5. 6. The source member is updated in the Map Model pane.

Type the member name in the Member Unique Name box in the Properties area. The source member is updated in the Map Model pane. Building Translation Maps .70 Universal Drill Through Guide Map Model pane. 8.

Creating a translation map . 2.Universal Drill Through Guide 71 Deleting member translations To delete a member translation: 1. You can add a Parent Translation Object only after you have added a level translation. the source cube might contain the member ’Q4’ in the Time dimension. Click Delete. Select the member translation in the Map Model pane. 2. Adding parent translations You might need to qualify a member with at least one parent member in order to make translation to the target universe possible. In this case. Select the level translation in the Map Model pane. To do this you need to add a Parent Translation object to the level. the context passed by the Drill Through Service would be ‘2000Q4’. For example. To add a Parent Translation Object: 1. Select Parent Translation in the Mapping Parts pane. The member translation is removed from the translation map. You would need to qualify the name of this member with the name of the parent member (for example ‘2000’) in order to create a unique member name.

4.72 Universal Drill Through Guide 3. The Drill Through Service will move up through the hierarchy of Parent Translation objects and qualify the level name with all the parent levels in the hierarchy. Deleting parent translations You delete a Parent Translation Object directly or by deleting the level or member translation to which it is associated. Specify the level to which the Parent Translation Object points by typing its name into the Unique Name box in the Properties area. Click Add. Building Translation Maps . Qualifying a translation with multiple parent levels You can qualify a level with more than one parent level by adding a Parent Translation object that points to a level that itself has a parent translation object. The Parent Translation object is added to the level. By default it points to the immediate parent level.

Type the name of the report in the Document Name box. The Document Information dialog box appears. 3. Creating a translation map . 2. Click Define Target Reports on the toolbar. 6. 4. Type a comment in the Comment box. Click Add. Type the document caption in the Document Caption box. 5. NOTE The caption and comment are optional. you need to specify the WebIntelligence target reports to which the map applies. Click OK.Universal Drill Through Guide 73 Specifying target reports After you have added the translations to the map. To do this: 1. The report appears in the Assigned Documents list.

3. Deleting a target report To remove a report from the target reports list: 1. Select the report in the Assigned Documents list. The Add button becomes a Set button.74 Universal Drill Through Guide Editing a target report To edit a target report: 1. 2. caption or comment as necessary. Building Translation Maps . Click Set. Select the report in the Assigned Documents list. The report is removed from the list. 2. Modify the document name. Click Remove.

Select a translation map and click OK. Working with existing translation maps . 2. you cannot open translation maps by double-clicking them in Windows Explorer. The translation map is loaded into UDS Designer.Universal Drill Through Guide 75 Working with existing translation maps You can use UDS Designer to open and modify an existing translation map. To open a translation map: 1. Because there is no file association between UDS Designer and UDM files. Select Open on the File menu. The Open Translation Map dialog box opens.

Select the cube that you want to connect to from the Cubes dropdown list box. (This step does not apply to MS OLAP. 7. Click Connect. you can change its source and/or target data sources. If connection is successful.76 Universal Drill Through Guide Changing the originating and target data sources After you have built a translation map. The OLAP Source Information dialog box appears. Building Translation Maps . 2. 3. To change the originating data source 1. Enter the name of the OLAP server in the OLAP Server box. Select the database containing the cube you want to access from the Databases dropdown list box.) 5. UDS Designer attempts to connect to the server using the information you have given. the DataBases dropdown list box is populated with names of the OLAP databases available on the server. 9. Click Change Originating Data Source on the Data Sources menu. Select the OLAP server type from the Server Type dropdown list. Enter your OLAP server username and password in the User Name and Password boxes. 4. Click Load Cube. 6. 8. The Cubes dropdown list box is populated with the names of all the cubes available in the database you selected.

Working with existing translation maps . The OLAP Source Information dialog box appears if your are working with an OLAP to OLAP map. the current map information is lost. To change the target data source 1. NOTE When you change the originating data source. Click Change Target Data Source on the Data Sources menu. or select the universe and click Change Originating Data Source to select a different universe. Follow the procedure outlined in To change the originating data source on page 76 to select a different OLAP cube. the translation map is populated with all the dimensions. 2. In addition. The Universe Target Information dialog box appears if you are working with an OLAP to relational map.Universal Drill Through Guide 77 The OLAP Source Information pane is populated with the dimensions. levels and hierarchies in the source cube. hierarchies and levels in the cube.

The Universal Drill Through Service Update dialog box appears. place your maps (*. Type the name of the server and the port number.UDM files) in the Data folder in your WebIntelligence installation. To do this. Click Update UDS on the toolbar. for example C:\Program Files\Business Objects\Business Objects Enterprise 6\OLAPData\UDSMaps. 2. You then need to stop and restart the WebIntelligence DTS Service to load the translation map. To do this: 1. then click Update. Building Translation Maps . you need to make them available to WebIntelligence so that the Drill Through Service can translate the user’s context when they click on a drillable cell.78 Universal Drill Through Guide Making translation maps available to WebIntelligence After you have built your translation maps.

WebIntelligence in Drill Through chapter .

WebIntelligence in Drill Through .80 Universal Drill Through Service Guide Overview This chapter concentrates on the WebIntelligence side of drill through. It looks at creating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report.

Universal Drill Through Service Guide 81 Creating WebIntelligence target reports Filters. Creating WebIntelligence target reports . The Drill Through Service deletes any existing filters on a report before applying drill filters. if you drill on the Fashion member of the Product dimension. and provide data at a more detailed level than the data in the cube. The resulting filter . a report already contains a filter restricting Country to ‘US’. conditions and prompts The Universal Drill Through Service applies drill contexts to target reports through the use of filters. then refreshing the list of corporate documents.Country = ‘US’ and ‘France’ . The sample source reports are based on the Retail2002 OLAP cube. then the Drill Through Service adds a filter restricting Country to ‘France’. Prompts Prompts work by applying filters to a report. The reports can then be accessed by users who need to drill through from OLAP cubes. Making target reports available for drill through You make target reports available by uploading them to the ’Corporate Documents’ area of WebIntelligence. rather than use existing reports that might contains filters that you want to retain. The Universal Drill Through Service applies filters to the reports depending on where the user chooses to drill in the source cube. Your target reports should not contain prompts on dimensions that are enabled for translation in the translation map. you should create new reports to use with drill through. the Drill Through Service applies a condition that restricts the Product dimension to Fashion. For example.returns no data. This is to avoid conflicting filters. As a result. For example. Sample target report The best way to understand drill through target reports and their relationship to source documents is to refer to the samples provided with WebIntelligence. The prompt filter might combine with the drill filter in the way described above to filter all data from the report.

the user might choose to drill down into sportswear revenues in California in Q1 2000 (measure cell) or drill down into fashion products (member cell). Where can the user drill in a report? UDS supports single or multiple-cell drill through from both measure and member cells.82 Universal Drill Through Service Guide Drill through workflow This section describes what happens in WebIntelligence when a user drills through from an OLAP cube to a universe. For example. Member cell Measure cell WebIntelligence in Drill Through .

Universal Drill Through Service Guide 83 Starting drill through To start drill through: 1. Cell selected for drill through Drill through workflow . Select the cell in the report. The cell is highlighted.

The Drill Through dialog box appears. WebIntelligence in Drill Through . 3.84 Universal Drill Through Service Guide 2. Select a target report from the list and click OK. Click the Drill Through button on the toolbar.

The target report In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000. sportswear. the target report displays sales revenue by product department by month by sales person within these restrictions.Universal Drill Through Service Guide 85 The target report opens at the context where you started drill through. They do not have to be contiguous in the report. The following examples show various multiple-selection scenarios and the the filters generated by the Drill Through Service. Drill through workflow . These cells can be values. and California. The Drill Through Service therefore applied filters to restrict the target report to 2000Q1. Drilling on multiple cells Drilling on multiple cells works on the same principle. As a result. The Drill Through Service builds a filter based on the cells you selected. members. or a combination of the two.

86 Universal Drill Through Service Guide EXAMPLE Selecting multiple measure cells In this situation the filter generated by the Drill Through Service is (2000 and Fashion) or (2000 and Work) EXAMPLE Selecting member labels from different dimensions In this situation the filter generated by the Drill Through Service is 100 and West WebIntelligence in Drill Through .

Universal Drill Through Service Guide 87 EXAMPLE Selecting member labels at the same level In this situation the filter generated by the Drill Through Service is West or Central EXAMPLE Selecting member labels from the same and different dimensions In this situation the filter generated by the Drill Through Service is 2001 and (Sportswear or Work) EXAMPLE Selecting member labels and values In this situation the filter generated by the Drill Through Service is ((2000 or 2001) and Fashion) or (2001 and Sportswear) Drill through workflow .

88

Universal Drill Through Service Guide

WebIntelligence in Drill Through

Managing and Maintaining a Drill Through Environment

chapter

90

Universal Drill Through Service Guide

Overview
This chapter describes the ongoing maintenance tasks that you will need to carry out to keep a drill through environment up-to-date and functioning correctly.

Managing and Maintaining a Drill Through Environment

Why maintenance is necessary . NOTE Remember that after you have modified a translation map. you need to stop and then restart the drill through service (see Making translation maps available to WebIntelligence on page 78). If the structure of your source cube or target cube/universe changes after you have installed your translation maps.Universal Drill Through Service Guide 91 Why maintenance is necessary You design your translation maps to work with the current structures of your source cubes and target cubes/universes. If you do not. but it is rare for the structure of databases to remain the same for long. it is likely that drill through will no longer work correctly. you will need to modify the maps to take account of the changes. You need to be aware of changes to both cube levels and individual cube members that might affect drill through.

If such members are added to the source cube. removed or renamed • Any universe class or object referenced by the translation map is removed or renamed Member changes Any of the above changes affect member translations also. you will need to add corresponding member translations to the translation map. You must also account for new members that require additional member-specific translation rules.92 Universal Drill Through Service Guide Changes that require updates Changes to either levels or specific members require that translation maps be updated. Level changes The following changes will require you to update your translation map: • A cube dimension is added. removed or renamed • A cube hierarchy is added. removed or renamed • A cube level is added. Managing and Maintaining a Drill Through Environment .

If additional levels. levels.Universal Drill Through Service Guide 93 Problems caused by outdated translation maps The problems caused by failing to update a translation map depend on the changes made to the source cube or target universe. Problems caused by outdated translation maps . or additional classes and objects are added in the target universe. hierarchy or level or a target universe class or object referenced by a translation map is removed or renamed. the Drill Through Service will simply ignore them because it will not be aware of their existence. hierarchies. drill through will fail. members are added in the source cube. If a source cube dimension.

You will not necessarily ’break’ a translation map by using different cubes and universes from the ones you used to build the map in the first place. Managing and Maintaining a Drill Through Environment . The same applies to target universes and cubes.94 Universal Drill Through Service Guide Source cube and target cube/universe locations Translation maps are based on cube and universe metadata. The source and target datasources must have the same names as the ones specified in the map (the Drill Through Service passes these names during drill through). but their physical locations are irrelevant. This means that any cube can be a drill through source as long as its metadata is compatible with the metadata in the translation map. not on the cubes and universes themselves.

13 F feedback on documentation 10 K Knowledge Base 12 C consultants Business Objects 11 customer support 11 M multimedia quick tours 10 O OLAP source cube design requirements 39 Online Customer Support 11 D demo materials 9 Developer Suite 10. ordering 9 roadmap 9 search 9 Documentation Supply Store 9 drill through and Business Objects 25 architecture 22-24 components 21-22 defined 20-21 previous difficulty of 24 drill through samples described 27 R relational database normalized 31 snowflake schema 32 star schema 32 S search documentation 9 support customer 11 T target database design requirements 35 designing 43 Essbase Accounts dimension 44 Essbase member-naming restrictions 44 E education see training Index . 12 documentation CD 9 feedback on 10 on the web 9 printed.Universal Drill Through Service Guide 95 Index B Business Objects consulting services 11. 13 documentation 10 Documentation Supply Store 9 support services 11 training services 11.

96 Universal Drill Through Service Guide target reports defined 18 target universe creating from the target database 46 design requirements 37 Tips & Tricks 10 training on Business Objects products 11 translation maps defined 17 U UDS 16. 34 relation to cubes 35 W web customer support 11 getting documentation via 9 useful addresses 12 WebIntelligence administrator required knowledge 19 tasks 17-18 Index . 21 UDS Designer 48-75 Universal Drill Through Service see UDS 16 universes 25.