Report Conversion Tool Guide

Transcription

1 Report Conversion Tool Guide BusinessObjects XI R2 Migration Pack 2 Windows

2 Patents Trademarks Copyright 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. 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. Copyright 2006 Business Objects. All rights reserved. Last update: October 2006

3 Contents Chapter 1 Using the Report Conversion Tool 5 Overview Installation Using the Report Conversion Tool Logging on Selecting and converting reports Exploring the repository Auditing the conversion session Publishing converted reports Chapter 2 Desktop Intelligence feature conversion 21 Overview Report features and conversion status Customizing the feature conversion status Features and their conversion status More on feature conversions Chapter 3 Calculations in Desktop Intelligence and Web Intelligence XI R2 43 Overview Detail objects and non-aggregative measures Extended dimension values Formula language differences Filtering differences Placing of dimensions Appendix A Audit table structure and data 59 The audit table Not converted documents Report Conversion Tool Guide 3

4 Contents Appendix B Business Objects Information Resources 63 Documentation and information services Documentation Customer support, consulting and training Useful addresses at a glance Index 69 4 Report Conversion Tool Guide

5 Using the Report Conversion Tool chapter

6 1 Using the Report Conversion Tool Overview Overview This guide explains how to use the Report Conversion Tool to convert Desktop Intelligence reports to Web Intelligence format on the BusinessObjects Enterprise XI R2 platform. The guide also describes the issues involved in report conversion. You use the Report Conversion Tool to convert the following types of report to Web Intelligence XI R2 (WID) format: Legacy BusinessObjects (REP) reports migrated to Desktop Intelligence (REP) format with the Import Wizard Desktop Intelligence reports created directly in Desktop Intelligence Note: Desktop Intelligence is the new name of the BusinessObjects product. It was first shipped under this new name in BusinessObjects Enterprise XI R2. What is the Report Conversion Tool? The Report Conversion Tool converts Desktop Intelligence XI R2 reports to Web Intelligence XI R2 format and publishes the converted reports to the CMS. The original Desktop Intelligence XI R2 report must also be in the same CMS. The tool does not convert all Desktop Intelligence reports, and it does not convert all Desktop Intelligence features. The level of conversion depends on the features in the original report. Some features prevent the report from being converted. Others features are modified, reimplemented or removed by the tool during conversion. 6 Report Conversion Tool Guide

7 Using the Report Conversion Tool Overview 1 Report statuses The tool assigns one of three statuses to each report: Fully Converted, Partly Converted, or Not Converted. The table below explains each status: Status Fully Converted Description The structure and format of the converted Web Intelligence report are identical to the structure and format of the original Desktop Intelligence report. Note: Although the source report and converted reports are structurally identical, the converted report might still return different values in certain circumstances. This is because the Web Intelligence calculation engine does not always interpret this structure in the same way as the Desktop Intelligence calculation engine. For more information, see Chapter 3: Calculations in Desktop Intelligence and Web Intelligence XI R2 Partly converted Some report features were converted to Web Intelligence, but not all. The unconverted features did not prevent the report as a whole from being converted. For more information, see Chapter 2: Desktop Intelligence feature conversion. Partly converted reports can also return different values due to calculation engine changes. Not converted The Desktop Intelligence report was not converted because it contains critical features that have no Web Intelligence equivalent. To help you understand which reports were not fully converted and why, the Report Conversion Tool can write audit data to a database of your choosing. You can examine this data directly in the database to understand the details of the conversion, or use the audit universe to generate reports on the data. Note: Designer must be installed to allow you to create the database connection that the Report Conversion Tool uses to write audit data. For more information on report features and conversion statuses, see Report features and conversion status on page 23. Report Conversion Tool Guide 7

8 1 Using the Report Conversion Tool Installation Determining which reports are fully or partly converted The Report Conversion Tool has an initialization file that allows you to determine which reports are flagged as Fully Converted and which are flagged as Partly Converted. This file allows you to customize the conversion process according to your particular needs. If, for example, you have numerous reports containing a feature that generates a default status of Partly Converted, but you do not consider conversion of this feature essential, you can edit the initialization file so that the feature no longer generates a Partly Converted status. For more information on the initialization file, see Customizing the feature conversion status on page 25. Installation User settings The Report Conversion Tool runs on Microsoft Windows platforms. It is installed by default when you run a Client or Server installation of BusinessObjects XI Release 2. When you run a Custom installation, you must select Report Conversion Tool to install it. You must also install Designer if either of the following apply: You want to write audit data about the conversion session to a database log. In this case you use Designer to define the connection to the audit database. For more information on auditing, see Auditing the conversion session on page 15. You want to convert free-hand SQL reports. In this case the Report Conversion Tool needs to access Designer to create free-hand SQL universes. For more information on free-hand SQL conversion, see Free-hand SQL on page 34. By default, users in the Administrators group or the Report Conversion Tool Users group have the rights to use the Report Conversion Tool. You can edit the user rights through the Central Management Console in the Business Objects Enterprise Applications > Report Conversion Tool section. For more information on the CMC and user rights, see the BusinessObjects Enterprise XI R2 Release 2 Administrator s Guide. 8 Report Conversion Tool Guide

9 Using the Report Conversion Tool Using the Report Conversion Tool 1 Using the Report Conversion Tool You perform the following tasks when working with the Report Conversion Tool: Step Log on and select the interface language Select and convert reports Audit the conversion session View conversion results and publish reports Description You log on to the Report Conversion Tool and select the language in which the interface will be displayed. See Logging on on page 10. You select the reports that you want to convert, then convert them to Web Intelligence XI R2 format. See Selecting and converting reports on page 10. You create an audit log (written to a database table in a database of your choosing) that gives details of the conversion. For more information, see Auditing the conversion session on page 15. For information on the audit table structure, see Appendix A: Audit table structure and data. You view the converted reports to evaluate the extent to which they have been converted, and publish the converted reports. For more information, see Publishing converted reports on page 18. For detailed information on which Desktop Intelligence features convert to Web Intelligence, and how the Report Conversion Tool performs the conversion, see Desktop Intelligence feature conversion on page 21. Report Conversion Tool Guide 9

10 1 Using the Report Conversion Tool Logging on Logging on To log on to the Report Conversion Tool 1. Click Start > Programs > BusinessObjects XI Release 2 > BusinessObjects Enterprise > Report Conversion Tool. 2. Click Available languages and select the interface language from the list if you want to change the interface language. 3. Enter the system, user ID, password and authentication mode (Enterprise, LDAP or Windows AD) and click OK. Selecting and converting reports You use the first screen in the Report Conversion Tool wizard to select reports for conversion. The pane on the left shows the repository in tree format. You select reports from the repository and move them to the list on the right for conversion. After you have selected reports for conversion, click Next at the bottom of the screen to start the conversion. The Conversion in Progress screen appears as the documents are being converted. This screen lists all the documents, together with their conversion status. Note: As well as listing the number of Fully Converted, Partly Converted and Not Converted documents, this screen also list the number of documents that could not be converted because of an error during the conversion process. Temporary documents During conversion, the Report Conversion Tool uses the Public Folders > Report Conversion Tool Documents > Report Conversion Tool Temporary Documents folder for temporary document storage. It creates subfolders with the name <login>_<system_name> to store these documents. For example, if you log on to a system called test using the Report Conversion Tool, and you use the login testuser, the folder name is testuser_test. Check the temporary documents folder periodically and delete any temporary documents that the Report Conversion Tool has not removed. 10 Report Conversion Tool Guide

11 Using the Report Conversion Tool Exploring the repository 1 Exploring the repository You can work in folder view or category view when exploring the repository. You can select reports from the following types of folders: your personal folders other user folders to which you have access rights favorites folders The folder types are displayed with the following icons: Folder type Public Icon Inbox Favorites The report statuses are displayed with the following icons: Icon Description Report has never been converted. Report has been fully converted. Report has been partly converted. Report could not be converted. (For more information on the report statuses, see Report statuses on page 7.) To explore the repository 1. Click Folders to view the repository by folder or click Categories to view the repository by categories. 2. To view the properties of a folder or category, right-click it, then select Properties from the menu. Report Conversion Tool Guide 11

12 1 Using the Report Conversion Tool Exploring the repository 3. To refresh the contents of a folder or category, right-click it, then select Refresh from the menu. 4. To view unconverted reports only, select Show unconverted reports only. Selecting reports for conversion You can select reports for conversion individually, by folder or by category. To select individual reports 1. Highlight the reports in the left pane and click >>, or right-click and select Add selected reports. The Report Conversion Tool adds the reports to the list of reports for conversion. 12 Report Conversion Tool Guide

13 Using the Report Conversion Tool Exploring the repository 1 To select reports by folder 1. Click Folders to view the repository by folder. 2. Select the folder that contains the reports you want to convert and rightclick. 3. Select Add all reports in this folder to all add all the documents in the folder to the list of reports for conversion. 4. Select Add all reports in this folder and subfolders to add all the documents in the folder and its subfolders to the list of reports for conversion. To select reports by category 1. Click Categories to view the repository by category. 2. Select the category that contains the reports you want to convert and right-click. 3. Select Add all reports in this category to all add all the documents in the folder to the list of reports for conversion. 4. Select Add all reports in this category and subcategories to add all the documents in the category and its subcategories to the list of reports for conversion. Searching for reports To search for a report 1. Type the name of the report in the search box below the list of folders/ categories. 2. Click the Search icon to the right of the search box. The Report Conversion Tool highlights the reports that correspond to your search. Note: You can search on partial report names. If you search on Sales2, you retrieve all reports whose name begins with Sales2, for example: Sales2004, Sales2005. Saving and opening lists of reports for conversion You can save the list of reports selected for conversion to a file (in XML format) and open this file later to populate the list. To save a list to a file 1. Click Save List. Report Conversion Tool Guide 13

14 1 Using the Report Conversion Tool Exploring the repository 2. Type the name of the file you want to create in the Save dialog box, then click OK. To open a saved list 1. Click Open List, then select the file you want to open from the list. The list of documents to convert is populated with the documents in the file. Converting reports containing free-hand SQL By default, the Report Conversion Tool does not convert documents containing free-hand SQL. To convert free-hand SQL reports, select Convert reports containing free-hand SQL. Note: Free-hand SQL conversion is possible only if Designer is installed on the same machine as the Report Conversion Tool. If you do not select this option, free-hand SQL documents appear as Not Converted at the end of the conversion process. For more information on how the Report Conversion Tool converts free-hand SQL reports, see Free-hand SQL on page 34. Note: The Report Conversion Tool cannot convert a free-hand SQL report unless a valid database connection for the free-hand SQL exists. 14 Report Conversion Tool Guide

15 Using the Report Conversion Tool Auditing the conversion session 1 Auditing the conversion session You can create an audit log to provide details of the conversion. The audit log is a database table (called OBJ_G_MIGRATION) that the Report Conversion Tool adds to the database you select for auditing. For information on auditing and database compatibility, see Auditing and database compatibility on page 16. For more information on the structure of the table, see Appendix A: Audit table structure and data. Defining the audit connection Before you can create an audit log, you must set up an audit connection to identify the database that will host the audit table. To do this you need to perform the following steps before running the Report Conversion Tool: Create the audit connection Assign the connection to the Report Conversion Tool To create the audit connection 1. Start Designer. 2. Select Tools > Connections. 3. Click Add. 4. Follow the steps in the New Connection Wizard to create the connection. See the Designer s Guide if you need more information. To assign the audit connection to the Report Conversion Tool 1. Log on to the Central Management Console. 2. Select BusinessObjects Enterprise Applications > Report Conversion Tool. 3. Select the connection in the list of connections and click Update. Note: You can also assign an audit connection from within the Report Conversion Tool. For more information, see To create the audit log on page 16. Creating the audit log You create the audit log in the second screen of the Report Conversion Tool, after you have converted your reports. Report Conversion Tool Guide 15

16 1 Using the Report Conversion Tool Auditing the conversion session To create the audit log 1. Select Audit the conversion. 2. Select the audit connection. By default, the connection assigned in the Central Management Console is selected. (For more information on assigning a connection in the CMC, see To assign the audit connection to the Report Conversion Tool on page 15.) 3. Select Delete existing audit table rows... if you want to clear existing data in the audit table before auditing the current conversion. Note: Only the rows previously written to the audit table by the current user are deleted. Rows written by other users remain in the table. 4. Select Append... if you want to add the current conversion data to the existing audit data. 5. Type a comment under Include this comment in each row written to the audit table if you want to add a comment to each row written to the audit table. 6. Click Next to write the audit data to the audit table. Auditing and database compatibility The following table lists the compatibility of the audit table and the audit universe with different RDBMS: RDBMS Audit table Audit universe Oracle Compatible Compatible MySQL Compatible Compatible Informix Compatible Compatible Sybase SQL Server See To create the audit Compatible table in a Sybase database on page 16. MS SQL Server Compatible Compatible DB2 Compatible Compatible Access Compatible See To modify the audit universe for an Access database on page 17. To create the audit table in a Sybase database 1. To allow the RCT to create the audit table in a Sybase database, run the following script: 16 Report Conversion Tool Guide

17 Using the Report Conversion Tool Auditing the conversion session 1 sp_dboption <database_name>,"ddl in tran ",true go This script tells Sybase to allow DDL statements within a transaction by setting the DDL In Tran property to true. (The default value is false.) The Report Conversion Tool issues the CREATE TABLE command from within a transaction. This action fails unless Sybase is set to allow DDL within a transaction. To modify the audit universe for an Access database 1. In the join expression for the G_MIG_C_USER column, change the UPPER function to UCASE as follows: UCASE(OBJ_G_MIGRATION.G_MIG_C_USER) = UCASE(@variable( BOUSER )) 2. Change the definition of the [Number of Documents] measure from count(distinct OBJ_G_MIGRATION.G_MIG_C_DOCNAME) to count(obj_g_migration.g_mig_c_docname). Note: Because you cannot use the COUNT and DISTINCT keywords in the same statement in Access, this workaround removes the DISTINCT keyword. You also need to modify the audit report so that the [Number of Documents] measure eliminates duplicate values. Report Conversion Tool Guide 17

18 1 Using the Report Conversion Tool Publishing converted reports Publishing converted reports After writing the conversion results to the audit database, you publish the converted results to the repository. A summary of the conversion results appears at the top of the screen, listing the percentages of Fully Converted, Partly Converted and Not Converted reports. You can also perform the following tasks before publishing the converted documents: Define the connection settings that allow you to view the converted reports in InfoView. Open original or converted reports Rename converted reports Change the categories of converted reports Change the folder in which a converted report is published. Note: By default, the Report Conversion Tool publishes converted reports in the same folder as the source report. To define the InfoView connection settings. 1. Right-click any row in the list of converted reports and select Set InfoView connection properties. 2. Set the connection protocol, host, port and web application in the Set InfoView Properties dialog box. To open an original or converted report in InfoView 1. Right-click the row showing the report and select Open original report or Open converted report on the menu. To rename a converted report 1. Right-click the Target name column on the row showing the report and click Rename converted report. 2. Type the new name. To change the categories of converted reports 1. Right-click the Target categories column on the row showing the report and click Change categories. 2. Click Publish in the following categories, then select the categories. 3. To return to the categories assigned to the original Desktop Intelligence report, follow step 1, then click Publish in the same categories as the original report. 18 Report Conversion Tool Guide

19 Using the Report Conversion Tool Publishing converted reports 1 To change the folder in which a converted report is published 1. Right-click the Target folder column on the row showing the report and click Change folder. 2. Click Publish in the following folder, then navigate to the folder. 3. Click OK. 4. To revert to the same folder as the original report, follow step 1, then select Publish in the same folder as the original report. Note: If you publish a converted report to a different folder than the original folder, the converted report inherits the security settings of the new folder. Ensure that these settings are consistent with the converted report. For example, users who will need to access the converted report must have access rights to the folder. To publish the converted reports 1. Click the checkbox in the left column next to the reports you want to publish, or click the checkbox in the column header to select all reports. 2. Click Next. The Publish Status screen tracks the progress as the Report Conversion Tool publishes the reports. 3. Click Close when publishing has finished. The Conversion Complete screen appears, giving a summary of the conversion session. 4. Click Return to Start to start another conversion session, or click Exit to exit the Report Conversion Tool. Report Conversion Tool Guide 19

20 1 Using the Report Conversion Tool Publishing converted reports 20 Report Conversion Tool Guide

21 Desktop Intelligence feature conversion Desktop Intelligence feature conversion chapter

22 2 Desktop Intelligence feature conversion Overview Overview This chapter provides detailed information on Desktop Intelligence features and how or whether they are converted into Web Intelligence. Use the information in this chapter in conjunction with the audit log generated by the conversion to understand how the Report Conversion Tool converted your reports. For details on the audit log file structure, see Appendix A: Audit table structure and data. 22 Report Conversion Tool Guide

23 Desktop Intelligence feature conversion Report features and conversion status 2 Report features and conversion status The level of similarity between a converted report and the original Desktop Intelligence report depends on the features in the original report. The Report Conversion Tool cannot convert all Desktop Intelligence features to Web Intelligence XI R2 because Web Intelligence XI R2 does not support all Desktop Intelligence features. The Report Conversion Tool marks reports as Fully Converted, Partly Converted or Not Converted depending on the features in the original report. Each feature in the original report has its own associated conversion status, and the most serious generates the overall status of the conversion. For example, if the original report contains a feature that cannot be converted and generates a Partly Converted status, the whole report is considered to be partly converted and the feature is not present in the Web Intelligence report. The presence of certain features in the original report means that the Report Conversion Tool cannot generate a Web Intelligence report. In this case the conversion status is Not Converted. Fully converted reports on page 23, Partly converted reports on page 24 and Not converted reports on page 24 give more information on the different conversion statuses. Features and their conversion status on page 28 lists all Desktop Intelligence features and their associated conversion status. More on feature conversions on page 34 provides specific details, where appropriate, of certain feature conversions and how they are handled by the Report Conversion Tool. Fully converted reports A fully converted report is structurally identical or almost identical to the original report, although some minor features or properties might have been lost in the conversion. Note: Although a fully converted report is structurally identical to the initial report, it might still return different figures after conversion in certain situations. This is because the Web Intelligence XI R2 calculation engine interprets the structure differently. For more information, see Chapter 3: Calculations in Desktop Intelligence and Web Intelligence XI R2. Some features not supported natively by Web Intelligence are reimplemented by the Report Conversion Tool in the Web Intelligence report. (For example, grouped variables in Desktop Intelligence are implemented with an If function in the converted Web Intelligence report - for more Report Conversion Tool Guide 23

24 2 Desktop Intelligence feature conversion Report features and conversion status information see Grouped variables on page 37.) The re-implemented feature behaves identically in Web Intelligence and does not affect the Fully Converted status. Partly converted reports Certain features in the original Desktop Intelligence report carry a default status of Partly Converted. If a report contains at least one feature that carries a Partly Converted status, the whole report is flagged as Partly Converted. You can modify this behavior by editing the Report Conversion Tool initialization file. This is useful if you have numerous reports containing a feature that generates a Partly Converted status by default, but you do not consider conversion of the feature important. In this case you edit the initialization file to set the associated status to Fully Converted. For more information on editing the initialization file, see Customizing the feature conversion status on page 25. Not converted reports If the Desktop Intelligence report contains a key feature that cannot be converted, the report is not converted. For example, if a report contains any data providers other than universes or free-hand SQL, it cannot be converted. 24 Report Conversion Tool Guide

25 Desktop Intelligence feature conversion Customizing the feature conversion status 2 Customizing the feature conversion status The Report Conversion Tool has an initialization file, in XML format, which allows you to determine the status generated by some report features. You can flag these features as Fully Converted or Partly Converted. The initialization file allows you to customize the conversion process according to your needs. If you have numerous reports containing a feature that generates a Partly Converted status during conversion, but you do not consider conversion of this feature important, you can edit the initialization file so that the feature generates a Fully Converted status. Note: You cannot control the status generated by all report features with the initialization file. If the table in Features and their conversion status on page 28 gives a hard-coded status instead of an initialization file setting, you cannot use the initialization file to change the status. Report Conversion Tool Guide 25

26 2 Desktop Intelligence feature conversion Customizing the feature conversion status Understanding the initialization file The initialization file is called errorlogsettings.xml and is stored in the $INSTALLDIR/win32_x86 folder. The file looks like this: <LOGMANAGER> <ERRORLOGS TARGET= FULLYCONVERTED > <!-- FILTER --> <ERROR TYPE= Filter/FilterFormula /> <!-- BREAK --> <ERROR TYPE= Breaks/ValueBasedBreaks /> <!-- DRILL --> <ERROR TYPE= Drill/QueryDrill /> <ERROR TYPE= Drill/MissingeRef /> <!-- GRAPH --> <ERROR TYPE= Graph/3DChart /> <ERROR TYPE= Graph/PieChart /> <ERROR TYPE= Graph/ElementPosition /> <ERROR TYPE= Graph/Pie3DChart /> <ERROR TYPE= Graph/General /> </ERRORLOGS> <ERRORLOGS TARGET= PARTLYCONVERTED > <!-- QUERY --> <ERROR TYPE= Query/Query /> <ERROR TYPE= Query/Keyword /> <ERROR TYPE= Query/QueryProp /> <ERROR TYPE= Query/QueryCond /> <ERROR TYPE= Query/Grouping /> etc... The table in Features and their conversion status on page 28 matches the feature references in the file (Filter/FilterFormula, for example) to features. Use the table to determine which entries to edit in the initialization file to customize the conversion process to your needs. Editing the initialization file By default, the file generates a Fully Converted status for some features (the errors listed in the <ERRORLOGS TARGET= FULLYCONVERTED > section) and a Partly Converted status for others (listed in the <ERRORLOGS TARGET= PARTLYCONVERTED > section). 26 Report Conversion Tool Guide

27 Desktop Intelligence feature conversion Customizing the feature conversion status 2 To change the status generated by a feature, move it to the appropriate section. For example, if you do not want a filter on a measure in a block to generate a Partly Converted status, move the corresponding element to the FULLYCONVERTED section as follows: <LOGMANAGER> <ERRORLOGS TARGET= FULLYCONVERTED > <ERROR TYPE= Filter/BlockMeasureFilter/> </ERRORLOGS>... </LOGMANAGER> Note: If an error is included in both sections, it generates a Fully Converted status. If an error is not included in either section, it generates a Partly Converted status. Report Conversion Tool Guide 27

28 2 Desktop Intelligence feature conversion Features and their conversion status Features and their conversion status Desktop Intelligence feature Data providers The following table lists Desktop Intelligence features and describes how they are handled by the Report Conversion Tool. The final column provides one of two types of information: The conversion status if the feature always generates the same status and this behavior cannot be customized The initialization file setting that determines whether the feature is flagged as Fully Converted or Partly Converted if this status can be customized For more information on the initialization file, see Customizing the feature conversion status on page 25. Result in Web Intelligence report Conversion status or initialization file setting OLAP data provider Report not converted. Not converted Personal data provider Report not converted. Not converted Stored procedure data Report not converted. Not converted provider XML data provider Report not converted. Not converted Universe data provider, where the universe is not found Report not converted. Not converted Free-hand SQL The SQL is moved to a derived table in a generated universe. See Free-hand SQL on page 34. Queries Filter with a Calculation Report not converted. operand FIlter with a Select Query Report not converted. Results operand (query on a query) Fully converted Not converted Not converted Automatic refresh setting Setting is lost. Partly converted 28 Report Conversion Tool Guide

29 Desktop Intelligence feature conversion Features and their conversion status 2 Desktop Intelligence feature Scope of analysis with filter on a measure Scope of analysis objects become result objects (see Scope of analysis and measure filters on page 36). Partly converted User objects User objects are lost. Partly converted An object whose definition includes the function The report cannot be refreshed. (See function on page 36.) Partly converted Sort in a query The sort is lost. Fully converted Delete Trailing Blanks Option is lost. Fully converted option set Do Not Retrieve Data Option is lost. Fully converted option set Document Properties Enhanced Viewing setting does not exist in Desktop Intelligence Filters Complex global or block filter Filter on a formula Filter in a block applied on a measure Sections Hide Section Header formula Hide Section Footer formula Special report contents Result in Web Intelligence report The Enhanced Viewing setting is enabled. The filter is lost in some cases (see Complex global and block filters on page 39). A variable is created and the filter applied to the variable (see Filter on a formula on page 38). Filter is lost. The formula is lost and the header is always visible. The formula is lost and the footer is always visible. Conversion status or initialization file setting Fully converted Filter/ComplexGlobalFilter or Filter/ComplexBlockFilter Fully Converted Filter/BlockMeasureFilter SectionFormat/HideHeader SectionFormat/HideFooter OLE object The object is lost. SpecialContent/OLE Report Conversion Tool Guide 29

30 2 Desktop Intelligence feature conversion Features and their conversion status Desktop Intelligence feature Picture The picture is lost. SpecialContent/Picture VBA macro The macro is lost. VBA/VBA Blocks Hide Block formula The formula is lost and the Partly converted block is always visible. Across Edge Display The settings are lost. Partly converted settings in crosstabs Page break header after Setting is lost. Partly converted page break setting Page break footer after page break setting Setting is lost. Partly converted Hide object (in the Block Pivot settings) Breaks Break on multiple dimensions Note: This refers to a break defined on more than one dimension, not a block that has multiple breaks on single dimensions. Object is lost from the block. The break is removed. Partly converted Breaks/ BreakOnMultipleDimension Break on an object not in The break is removed Breaks/BreakObjectNotInBlock the block Folded break The break is unfolded Breaks/FoldedBreak Value-based break The break is removed Breaks/ValueBasedBreaks Pages Page setup options Original page setup options are lost and default Web Intelligence page options applied. Fully converted Functions Result in Web Intelligence report Conversion status or initialization file setting 30 Report Conversion Tool Guide

31 Desktop Intelligence feature conversion Features and their conversion status 2 Desktop Intelligence feature ApplicationValue BlockNumber CurrentPage DataProviderType GetProfileNumber GetProfileString Hyperlink Multicube OLAPQueryDescription PageInSection Product CountAll Dates All date formats Relative dates Result in Web Intelligence report Appears as RepFormula ( original_syntax ) For more information, see Unsupported functions on page 37. Converted to Web Intelligence syntax. For more information, see CountAll function on page 37. Changed to an equivalent Web Intelligence format according to the mappings given in Date format mapping on page 35. Implemented with the RelativeDate function. For more information, see Relative dates on page 41. Formula/UnsupportedFunction Partly converted Fully converted Fully converted Cell format Fill character The fill character is lost. Fully converted Hide cell formula (freestanding cells) The hide cell formula is lost and the cell is always visible. Conversion status or initialization file setting FormatCell/Appearance Report Conversion Tool Guide 31

32 2 Desktop Intelligence feature conversion Features and their conversion status Desktop Intelligence feature Border styles Variables All variables Variable that references another variable that cannot be converted Grouped variables. Sorts A block sorted on an object not included in the block Charts Multiple groups 3D Pie Charts 3D Charts Series color Rotation, elevation and start angle Plot area Wall color Result in Web Intelligence report Converted according to the mappings given in Border styles on page 39. The variable description is lost. Report not converted The grouped variable is implemented with an If function. For more information, see Grouped variables on page 37. The sort is lost. The first group only appears. There is no plot area in Web Intelligence 3D Pie charts There is no plot area in Web Intelligence 3D charts The original relationship between a series and its color is lost. For more information, see Series color on page 41. These settings are lost in Web Intelligence. The plot area does not exist in Web Intelligence pie charts and 3D charts. All walls have the same color in Web Intelligence. Conversion status or initialization file setting Fully converted Fully converted Not converted Fully converted Partly converted Graph/MultiGroupChart Graph/Pie3DChart Graph/3DChart Fully converted Fully converted Fully converted Fully converted 32 Report Conversion Tool Guide

33 Desktop Intelligence feature conversion Features and their conversion status 2 Desktop Intelligence feature Save options Result in Web Intelligence report Conversion status or initialization file setting Write password or protection password set Fonts Font mapping Report not converted. Fonts are mapped between Desktop Intelligence and Web Intelligence according to customizable rules. For more information, see Font mapping on page 40. Not converted Fully converted Report Conversion Tool Guide 33

34 2 Desktop Intelligence feature conversion More on feature conversions More on feature conversions Free-hand SQL This section provides additional details of the more complex feature conversions listed in the table in the section Report features and conversion status on page 23. Web Intelligence XI R2 does not support free-hand SQL. The Report Conversion Tool converts free-hand SQL documents by creating universes with derived tables that contain the free-hand SQL. Each free-hand SQL query has a derived table. The report objects that were based on the freehand SQL in the source report are based on the derived table in the Web Intelligence XI R2 report. The Report Conversion Tool creates free-hand SQL universes in the Report Conversion Tool Universes subfolder of the root universe folder in the CMS. Note: A derived table is a universe table that is based on an SQL query rather than a physical table in the database. It is the universe equivalent of a view in a relational database. For more information on derived tables, see the Designer Guide. The Report Conversion Tool creates Free-Hand SQL universes and connections as follows: Universes are called FHSQLXXX. There is one universe for each free-hand SQL data source. Free-hand SQL universe connections are called FHSQLXXX_<original_freehand_SQL_connection_name> Note: If more than one free-hand SQL connection points to the same data source, the Report Conversion Tool uses the first connection name that it encounters to name the universe connection. Different free-hand SQL queries against the same data source are stored in the universe based on that data source as derived tables called ClassX. Objects based on a derived table are stored in a class with the same name as the derived table. Example: Converting multiple free-hand SQL documents In this example you have five documents based on free-hand SQL queries. The first two (sales_rpt1 and sales_rpt2) are based on a database called sales and the free-hand SQL connection is called sales. 34 Report Conversion Tool Guide

35 Desktop Intelligence feature conversion More on feature conversions 2 The second two (emp_rpt1 and emp_rpt2) are based on a database called employees and the free-hand SQL connection is called emp. The fifth (emp_rpt3) is also based on the employees database, but the freehand SQL connection is called employee. After conversion, the documents, universes, connections and derived tables are as follows: WID document Universe Connection Derived table/ Query object class sales_rpt1 FHSQL001 FHSQL001_sales Class1 sales_rpt2 FHSQL001 FHSQL001_sales Class2 emp_rpt1 FHSQL002 FHSQL002_emp Class1 emp_rpt2 FHSQL002 FHSQL002_emp Class2 emp_rpt3 FHSQL002 FHSQL002_emp Class 3 Date format mapping All Desktop Intelligence functions using Date formats as a parameter are converted using the following mapping: Desktop Intelligence format Web Intelligence format AM/PM, AM/pm, AM/Pm, AM/pM A am/pm, am/pm, am/pm, am/pm, am/pm, am/pm, a or A am/pm, am/pm Am/pm, Am/PM, Am/Pm, Am/pM a or A DDDD, DDDd, DDdD, DDdd DDDD dddd, dddd, dddd, dddd, dddd, dddd, dddd, dddd dddd Dddd, DdDD, DdDd, DddD Dddd DDD, DDd DDD ddd, ddd, ddd, ddd ddd Ddd, DdD Ddd dd, DD, dd, Dd dd d, D d Report Conversion Tool Guide 35

36 2 Desktop Intelligence feature conversion More on feature conversions Desktop Intelligence format HH HH H H hh, hh hh h h mm, MM, mm, Mm MM M, m M MMMM, MMmm, MMmM, MMMm MMMM mmmm, mmmm, mmmm, mmmm, mmmm, mmmm, mmmm mmmm, mmmm Mmmm, MmMm, MmMM, MmmM Mmmm MMM, MMm MMM mmm, mmm, mmm, mmm mmm Mmm, MmM Mmm ss, SS, Ss, ss ss s, S s yyyy, yyyy, yyyy, yyyy, yyyy, yyyy, yyyy, yyyy, yyyy Yyyy, YYYY, YYYy, YYyY, YYyy, YyYY, YyYy, YyyY yy, YY, Yy, yy yy Web Intelligence format Queries Scope of analysis and measure filters If a Desktop Intelligence query contains a condition on a measure and a scope of analysis, then the converted Web Intelligence query groups (in the Result Objects section) all objects from the Desktop Intelligence results (objects and scope of analysis). This maintains the same query results. function Some objects contain a reference to the function in their definition. This function returns the value of a VBA macro. Web Intelligence XI R2 does not support either function or VBA macros. If a query contains an object with a reference the report cannot be refreshed. 36 Report Conversion Tool Guide

37 Desktop Intelligence feature conversion More on feature conversions 2 Formulas and functions Unsupported functions If Web Intelligence XI R2 does not support a function or keyword used in a Desktop Intelligence formula, the original formula appears as an argument to the special Web Intelligence function RepFormula as follows: RepFormula( original_formula_syntax ) The RepFormula function generates the #REPFORMULA message in Web Intelligence. Example: The BlockNumber function A Desktop Intelligence report contains the BlockNumber function, which is not supported by Web Intelligence XI R2. This formula is changed to =RepFormula("=BlockNumber()") in the Web Intelligence report, and Web Intelligence displays the #REPFORMULA message in the cell containing this formula. This mechanism is recursive (if VariableA is built using VariableB, and if VariableB is converted using the RepFormula() function, then VariableA will be converted using the Repformula() function). CountAll function The Desktop Intelligence function CountAll is converted to Web Intelligence using the following syntax: Desktop Intelligence syntax CountAll(<Object>) Web Intelligence syntax Count ([Object];INCLUDEEMPTY;ALL) Variables Grouped variables A grouped variable in a Desktop Intelligence report is implemented in the Web Intelligence report with an If formula. Example: Grouped variables in Web Intelligence Report Conversion Tool Guide 37

38 2 Desktop Intelligence feature conversion More on feature conversions You have a grouped variable called Resort Group in your Desktop Intelligence report. This variable is based on the Resort dimension and it has the following values: Resort Grouping Resort Group values Australian Reef <no grouping> Australian Reef French Riviera French Resorts French Resorts Bahamas Beach US Resorts US Resorts Hawaiian Club US Resorts US Resorts Royal Caribbean US Resorts US Resorts This grouping s implemented in Web Intelligence as a variable called Resort Group which has the following formula: If(([Resort] InList("Bahamas Beach";"Hawaiian Club";"Royal Caribbean"));("US Resorts");If( ([Resort] InList("French Riviera"));("French Resorts");[Resort])) Filters Filter on a formula If the Desktop Intelligence report contains a formula to which a filter is applied, the Report Conversion Tool creates a variable based on the formula, places it in the cell originally containing the formula, and applies the filter to the variable. These variables are named in the form TurnedToVariable_n. As a result, if the original report contains three formulas with filters applied, the converted report contains the variables TurnedToVariable_1, TurnedToVariable_2 and TurnedToVariable_3. 38 Report Conversion Tool Guide

39 Desktop Intelligence feature conversion More on feature conversions 2 Filter on a measure If a block is filtered on the values of a measure, the filter is removed during conversion. Example: Filter on a measure You have a report containing the following data and you apply the filter Revenue = , which restricts the block to showing the first row only. Country Revenue US 2,451,104 France 835,420 When the report is converted to Web Intelligence the filter is removed, and the block shows both rows. Complex global and block filters Global filters and block filters are converted only if they have the following format: <filtered_object><operator><constant or list_of_values> For example, if a block is filtered on the Country object by <Country> <> France, the Report Conversion Tool is able to convert the filter. Any global or block filter that does not correspond to this format is a complex filter and is not converted. For example, the formula <Revenue> > <Average_Revenue> is not converted because it compares the filtered object against another object rather than against a constant or list of values. Cell format Border styles Some Desktop Intelligence border styles do not exist in Web Intelligence. In such a case, default borders and no pattern are used in the generated Web Intelligence report. The log file does not list all cells impacted by this format reduction. The following table shows how Desktop Intelligence border styles are converted to Web Intelligence: Report Conversion Tool Guide 39

40 2 Desktop Intelligence feature conversion More on feature conversions This Desktop Intelligence border style None Thin, medium, small dotline, medium dotline, long dotline Bold Extra bold, double line, double dotline Becomes this style in Web Intelligence None Thin Bold Extra bold Fonts Font mapping The following Desktop Intelligence fonts can be converted to Web Intelligence: Arial, Courier New, Fixedsys, Impact, MS Serif, Helvetica, Tahoma, Times New Roman, BOJapan, default All other fonts are switched to the default font in the converted Web Intelligence report. The default font used by Web Intelligence is dependant on the locale and is set by the administrator. You can change the font mapping by editing the <FONTMAPPING> section in the SETTINGS.XML file in the following directory: $INSTALLDIR\BusinessObjects Enterprise 11.5\win32_x86 Example: Change the font mapping Open the settings.xml file with any XML editor and add the following lines to change the mapping for Courier and Verdana: <FONTMAPPING> <FONT SOURCE="Courier" TARGET="Courier New" /> <FONT SOURCE="Verdana" TARGET="Tahoma" /> </FONTMAPPING> Note: All fonts that appear in the <FONTMAPPING> section must also appear in the <SERVERFONTS> section above it. 40 Report Conversion Tool Guide

41 Desktop Intelligence feature conversion More on feature conversions 2 Charts Series color Desktop Intelligence allows you to associate colors with data series. The converted Web Intelligence report does not maintain this association and the original colors are replaced with colors from the default Web Intelligence color palette. This first series is assigned the first color in the palette, the second series is assigned the second color in the palette, and so on. Dates Relative dates Relative dates can be expressed in the form [date] +/- [number] in Desktop Intelligence. For example, <Invoice Date> + 2 refers to two days after the date in <Invoice Date>; <Arrival Date> - 5 refers to five days before the date in <Arrival Date>. Web Intelligence defines relative dates using the RelativeDate function and the Report Conversion Tool converts relative dates to this format. The previous examples appear in the converted report as follows: Desktop Intelligence syntax <Invoice Date> + 2 <Arrival Date> - 4 Web Intelligence syntax RelativeDate([Invoice Date];2) RelativeDate([Arrival Date];-5) Report Conversion Tool Guide 41

42 2 Desktop Intelligence feature conversion More on feature conversions 42 Report Conversion Tool Guide

43 Calculations in Desktop Intelligence and Web Intelligence XI R2 chapter

44 3 Calculations in Desktop Intelligence and Web Intelligence XI R2 Overview Overview Chapter 1: Using the Report Conversion Tool explains how to convert reports from Desktop Intelligence format to Web Intelligence XI R2 format using the Report Conversion Tool. After conversion, some reports that the Report Conversion Tool identifies as Fully Converted might still return different results in certain circumstances from the results returned by the original report. This happens because the calculation engine (the part of the software that calculates report results) does not always behave identically in Desktop Intelligence and Web IntelligenceXI R2. A Fully Converted report is a report whose structure is identical to the structure of the original report. Even so, the new calculation engine sometimes interprets this structure differently. This chapter helps you to identify reports that might be affected by calculation engine behavior, to understand the differences that this behavior produces, and, where possible, to make manual modifications to bring your converted reports in line with your original reports. The calculation engine differences fall into the following categories: Category Formula language differences Filter differences Detail objects and nonaggregative measures Placing of dimensions Details Some Web Intelligence functions do not always return the same value as the equivalent Desktop Intelligence function, and the two formula languages are not always identical. For more information, see Formula language differences on page 49. Web Intelligence does not always filter in the same way as Desktop Intelligence. For more information, see Filtering differences on page 54 Desktop Intelligence and Web Intelligence treat detail objects differently in some situations. For more information, see Detail objects and non-aggregative measures on page 46. Dimensions sometimes return different values in Desktop Intelligence and Web Intelligence, depending on where they are placed in a report. For more information, see Placing of dimensions on page Report Conversion Tool Guide

45 Calculations in Desktop Intelligence and Web Intelligence XI R2 Overview 3 Note: As a general rule, you should pay careful attention to reports with synchronized data providers. They are much more likely to be affected by calculation engine changes than reports with a single data provider. Migration, conversion and calculation differences You use the Import Wizard to migrate Desktop Intelligence documents to Desktop Intelligence during migration to BusinessObjects Enterprise XI R2. You can then use the Report Conversion Tool to convert these documents to Web Intelligence XI R2 format (this process is described in Chapter 1: Using the Report Conversion Tool) or you can work with them in Desktop Intelligence. Calculation engine behavior differs between some versions of Desktop Intelligence (earlier versions of Desktop Intelligence before the product name change in XI R2) in addition to differing between Desktop Intelligence and Web Intelligence XI R2. This is covered in the BusinessObjects 6.x to XI Release 2 Migration Guide, in the chapter Checking Imported Documents. You should read it to understand how your Desktop Intelligence report might already differ from your original Desktop Intelligence report even before you use the Report Conversion Tool. (The exact differences depend on the version of Desktop Intelligence you were using before migration to Desktop Intelligence.) If you then convert the report to Web Intelligence XI R2, you should read this chapter to understand the additional changes in Web Intelligence. The following table summarizes migration and conversion of Desktop Intelligence reports from an earlier version to BusinessObjects Enterprise XI R2: Source Report BusinessObjects 5.x/6.x report (REP) Desktop Intelligence report (REP) Transformation Tool Import Wizard Report Conversion Tool New Report Desktop Intelligence report (REP) Web Intelligence XI R2 report (WID) Calculation Differences Depends on source report version. See Migration Guide See this chapter for more information. Examples Unless otherwise noted, the examples in this chapter are created from the Island Resorts Marketing universe shipped with BusinessObjects XI R2. Report Conversion Tool Guide 45

46 3 Calculations in Desktop Intelligence and Web Intelligence XI R2 Detail objects and non-aggregative measures Detail objects and non-aggregative measures A detail is a universe object that is associated with a dimension. The detail provides further information about the dimension. For example, Age is a detail of the Customer dimension in the Island Resorts Marketing universe. Desktop Intelligence allows multiple values of a detail object for one value of the associated dimension when the dimension and detail are placed in the same block. Desktop Intelligence also takes the detail values into account when calculating measures: if the value of a measure is given by the combination of dimension value plus detail value, this is the value that Desktop Intelligence displays. By default, Web Intelligence allows only one detail value for each dimension value, and Web Intelligence does not take the detail into account when calculating measures. If you place a dimension and detail in a block in a Web Intelligence report and the objects have a one-to-many relationship, the detail returns the #MULTIVALUE error and Web Intelligence calculates any related measures solely around the dimension value. You solve this by creating a variable of dimension type which references the detail, and replacing the detail with the variable. For example, if you have a detail called Age, you replace it with a variable of dimension type whose formula is =Age. Note: Although enabling the Avoid Duplicate Row Aggregation block property sometimes solves the problem of multi valued detail objects in simple situations, you should not use this property as a solution to this problem. It is a solution that works only in extremely simple reports. Example: A dimension with multiple detail values This example illustrates in general terms the differences between Desktop Intelligence and Web Intelligence behavior. Desktop Intelligence: Dimension Detail Measure Dimension Value 1 Detail Value Dimension Value 1 Detail Value Dimension Value 1 Detail Value Dimension Value 2 Detail Value Report Conversion Tool Guide

47 Calculations in Desktop Intelligence and Web Intelligence XI R2 Extended dimension values 3 Web Intelligence with a multi valued detail object: Dimension Detail Measure Dimension Value 1 #MULTIVALUE 900 Dimension Value 2 Detail Value Web Intelligence with a dimension object that references a multi valued detail: Dimension Detail Dimension Measure Dimension Value 1 Detail Value Dimension Value 1 Detail Value Dimension Value 1 Detail Value Dimension Value 2 Detail Value Non-aggregative measures Web Intelligence applies the same rule to non-aggregative measures. (A nonaggregative measure is a measure that does not have an associated aggregation method - for example Sum - defined in the universe.) If the measure has multiple values for one value of a dimension in the same block, Web Intelligence displays #MULTIVALUE in the measure cell. Extended dimension values Desktop Intelligence extends the values in a synchronized dimension with the values in the other dimensions with which it is synchronized. This means that Desktop Intelligence returns a dimension value when a block contains an associated measure value, even when the dimension is not explicitly placed in the block. In other words, Desktop Intelligence returns dimension values for all dimensions in the synchronization. Web Intelligence does not do this by default. To make Web Intelligence extend dimension values, you enable the Extend merged dimension values document property. Example: Extending dimension values This example illustrates the difference between Desktop Intelligence and Web Intelligence default behavior. You have a report with the following three data providers: Report Conversion Tool Guide 47

48 3 Calculations in Desktop Intelligence and Web Intelligence XI R2 Extended dimension values Data Provider 1: Country of origin Future Guests France 28 Data Provider 2: Country of origin Future Guests Germany 21 Data Provider 3: Country of origin Future Guests Japan 9 If you combine Country of Origin from DP1 and Future Guests forms DPs 1, 2 and 3 in a block, Desktop Intelligence returns the following result: Country (DP1) Future Guests (DP1) France 28 Future Guests (DP2) Germany 21 Japan 9 Future Guests (DP3) Without the Extend merged dimension values option, Web Intelligence returns the following result: Country (DP1) Future Guests (DP1) France 28 Future Guests (DP2) Future Guests (DP3) Although the block contains measures associated with other merged dimensions, by default Web Intelligence shows only those values from the dimension explicitly placed in the block. With the Extend merged dimension values option enabled, Web Intelligence returns the same result as Desktop Intelligence. 48 Report Conversion Tool Guide

49 Calculations in Desktop Intelligence and Web Intelligence XI R2 Formula language differences 3 Formula language differences Running functions and sort order In Web Intelligence the running functions (RunningCount, RunningSum, RunningAverage, RunningProduct) rely on the sort order. In Desktop Intelligence they do not: Desktop Intelligence uses the previous value of the measure irrespective of the sort order. Example: Running functions in Desktop Intelligence and Web Intelligence In this example, a Desktop Intelligence report contains the formula RunningSum(<Revenue>,<Quarter). In Desktop Intelligence this formula produces the following result: Country Year Quarter Revenue RunningSum France FY1998 Q1 76,270 76,270 France FY1998 Q1 85,560 85,560 France FY1998 Q3 81,085 81,085 France FY1998 Q4 53,025 53,025 France FY1999 Q1 70, ,670 The figure for Q is 146,670 (76, ,400), which Desktop Intelligence calculates even though the two revenue values do not appear consecutively in the block. In Web Intelligence the block appears as follows: Country Year Quarter Revenue RunningSum France FY1998 Q1 76,270 76,270 France FY1998 Q1 85,560 85,560 France FY1998 Q3 81,085 81,085 France FY1998 Q4 53,025 53,025 France FY1999 Q1 70,400 70,400 Report Conversion Tool Guide 49

50 3 Calculations in Desktop Intelligence and Web Intelligence XI R2 Formula language differences The block returns the same value as Desktop Intelligence only when it is sorted by quarter. Country Year Quarter Revenue RunningSum France FY1998 Q1 76,270 76,270 France FY1999 Q1 70, ,670 Running functions and default reset contexts Web Intelligence does not reset running functions by default in the same way as Desktop Intelligence. The following table summarizes the differences: Report element Desktop Intelligence Web Intelligence Section break No Reset Reset Table break No Reset No Reset Example: Running function and a section break Desktop Intelligence does not reset the calculation across the break: France Resort Revenue RunningSum French Riviera 835, ,420 US Resort Revenue RunningSum Bahamas Beach 971, ,864 Hawaiian Club 1,479,660 3,286, Report Conversion Tool Guide

51 Calculations in Desktop Intelligence and Web Intelligence XI R2 Formula language differences 3 Web Intelligence does: France Resort Revenue RunningSum French Riviera 835, ,420 US Resort Revenue RunningSum Bahamas Beach 971, ,444 Hawaiian Club 1,479,660 2,451,104 The Count function and empty values Desktop Intelligence and Web Intelligence functions define empty values differently. This impacts the totals returned by the CountAll/Count function when empty values appear in the list of values to be counted. Note: This issue affects to the CountAll function in Desktop Intelligence and the Count function with the IncludeEmpty and All arguments in Web Intelligence. These syntaxes are functionally equivalent. Desktop Intelligence regards only null values returned from the database as empty values. Web Intelligence also regards empty values created in a block as a result of client-side processing as empty. Example: The Count function and empty values In this example you have a data provider that contains the following objects: Country, Year, Reservation Year, Revenue, Future Guests. There is a query filter restricting Reservation Year to FY2003 This query generates two SQL statements whose results are synchronized by the calculation engine. If you place the objects in a block as follows, the block contains empty values in the Future Guests column. Country Year Revenue Future guests France FY , France FY , France FY , US FY ,614 Report Conversion Tool Guide 51

52 3 Calculations in Desktop Intelligence and Web Intelligence XI R2 Formula language differences Country Year Revenue Future guests US FY ,930 US FY ,560 Count: 1 or 2 These empty values are the result of calculation engine processing; they are not null values returned from the database. As a result, Desktop Intelligence ignores them and the count returns 1. Web Intelligence includes them and returns 2. Note: The equivalent formulas are CountAll(<Future guests>) in Desktop Intelligence and Count([Future guests];includeempty;all) in Web Intelligence. Referencing data outside sections The Desktop Intelligence formula language allows you to refer to data outside the current section in a report with sections. The Web Intelligence formula language, with the exception of the Report keyword, does not. Example: Referring to data outside the current section In the report below, the free-standing cell below the block contains the formula Sum(<Revenue>) Where (<Country> = US ): France Resort Revenue French Riviera 835,420 2,451,104 or blank US Resort Revenue Bahamas Beach 971,444 Hawaiian Club 1,479,660 2,451, Report Conversion Tool Guide

53 Calculations in Desktop Intelligence and Web Intelligence XI R2 Formula language differences 3 In Desktop Intelligence the cell returns the total revenue for the US even when it appears in the France section. In Web Intelligence this cell is blank because the formula cannot reference data outside the current section. Note: The formula Sum([Revenue] In Report) returns the same value in Desktop Intelligence and Web Intelligence because you can use the Report keyword to access data outside the current section. Report Conversion Tool Guide 53

54 3 Calculations in Desktop Intelligence and Web Intelligence XI R2 Filtering differences Filtering differences Block filters When you filter on a block, Desktop Intelligence applies the filter on the data in the underlying cube. Web Intelligence applies the filter to the data in the block. Example: Block filters In this example you have a data provider with the objects Country, Year and Revenue and you create a block containing Country and Revenue: Country Revenue France 835,420 US 2,451,104 If you apply the filter Revenue >=2,000,000 on the block, the block returns no rows in Desktop Intelligence, because Desktop Intelligence applies the filter on the values in the cube (revenue by country and resort) rather than in the block. The cube values are as follows: Country Resort Revenue France French Riviera 835,420 US Bahamas Beach 971,444 US Hawaiian Club 1,479,660 None of these values is >= 2,000,000, which is why the block returns no rows. In Web Intelligence the filter produces this result: Country Revenue US 2,451,104 This is because Web Intelligence filters on the result objects (the objects in the block), and only US has a revenue >= 2,000, Report Conversion Tool Guide

55 Calculations in Desktop Intelligence and Web Intelligence XI R2 Filtering differences 3 Indirect filters Web Intelligence and Desktop Intelligence apply report filters differently when a report contains multiple data providers and those data providers are synchronized (through linking in Desktop Intelligence and merged dimensions in Web Intelligence). When you a apply a report-level filter, Desktop Intelligence also applies this filter indirectly; Web Intelligence does not. Example: Indirect filters In this example you have a report with two data providers synchronized on the Country dimension: DP1: Country, Revenue DP2: Country, Reservation Year, Future Guests You create a report with two blocks: Country Revenue France 835,420 US 2,541,104 Country Reservation Year Future guests France FY France FY France FY US FY US FY If you apply a report filter that restricts Reservation Year to FY2003, Desktop Intelligence automatically filters the first table in addition to the second: Country Revenue France 835,420 Country Reservation Year Future guests France FY Why? Desktop Intelligence applies an indirect filter to the first table because it is linked to the second table through the Country dimension. When you apply the report filter on Reservation Year, this removes all values of Country except France from the second table. Desktop Intelligence then carries this filter through to the first table. Report Conversion Tool Guide 55

56 3 Calculations in Desktop Intelligence and Web Intelligence XI R2 Placing of dimensions Web Intelligence does not apply the indirect filter. The first table remains unchanged even when you apply the filter on Reservation Year. Placing of dimensions Dimensions and sections If you place a free-standing cell in a section and the cell content is a dimension contained in the section, Desktop Intelligence always returns the #MULTIVALUE error. Web Intelligence returns #MULTIVALUE if the dimension has more than one value in the section. If it has one value only, Web Intelligence returns that value. Example: Free-standing cell in a section In this example you have a data provider containing the Country, Year and Revenue objects. You create a report with year as the section header and a block showing country and revenue in each section: FY1998 Country Revenue France 295,940 US 767,614 If you place a free-standing cell within the section and below the block, and set the cell formula to =<Country> (=[Country] in Web Intelligence), the cell returns #MULTIVALUE in both Desktop Intelligence Web Intelligence. Now you apply a query filter that restricts Country to France : FY1998 Country Revenue France 295,940 #MULTIVALUE or France In this case, Desktop Intelligence still returns #MULTIVALUE in the freestanding cell. Web Intelligence returns France, because the Country dimension now has one value only in each section. 56 Report Conversion Tool Guide

57 Calculations in Desktop Intelligence and Web Intelligence XI R2 Placing of dimensions 3 Dimensions in block headers and footers When you place a dimension in a block header in Desktop Intelligence, the cell returns the minimum value of the dimension. When you place a dimension in a footer, the cell returns the maximum value of the dimension. In Web Intelligence, dimensions placed in block headers or footers return #MULTIVALUE. Example: Dimensions in block headers and footers You place the Country dimension in the header and footer of block in a Desktop Intelligence report to produce the following result: Australia Australia France Germany Holland Japan UK US US The formula for the header and footer is =<Country>. In the header this returns Min(<Country>) and in the footer Max(<Country>). In Web Intelligence the block appears as follows: #MULTIVALUE Australia France Germany Holland Japan UK US #MULTIVALUE Report Conversion Tool Guide 57

58 3 Calculations in Desktop Intelligence and Web Intelligence XI R2 Placing of dimensions 58 Report Conversion Tool Guide

59 Audit table structure and data Audit table structure and data appendix

60 Audit table structure and data A The audit table The audit table The audit table is called OBJ_G_MIGRATION and contains the following columns and data: Column G_MIG_C_LOGDATE G_MIG_C_DOCNAME G_MIG_C_STATUS G_MIG_C_LOGENTRY G_MIG_C_SEVERITY G_MIG_C_CAUSE G_MIG_C_TYPE G_MIG_C_SUBTYPE Description The date on which the conversion was run. The name of the Desktop Intelligence document. The conversion status. Values are: Not converted - the document could not be converted to Desktop Intelligence format. Partly converted - the document was converted, but a feature could not be converted. Fully converted - the document was fully converted to Web Intelligence. Note: A fully-converted document might still return different calculation results from the original document in certain circumstances. For more information, see Chapter 3: Calculations in Desktop Intelligence and Web Intelligence XI R2 The row number per document. (A single document can generate multiple rows in the table.) The severity of the problem. Possible values are: Error - the document could not be converted. Warning - the document was converted but a document feature could not be converted. Advisory - a document feature could not be converted; the effect of non-conversion is less than in the case of Warning. The cause of the error, warning or advisory. The general type of problem that caused the error, warning or advisory. The specific problem that caused the error, warning or advisory. 60 Report Conversion Tool Guide

61 Audit table structure and data The audit table A Column G_MIG_C_ERRORTEXT G_MIG_C_FOCUS G_MIG_C_KEYWORD G_MIG_C_RESULT G_MIG_C_WORKAROUND G_MIG_C_USER G_MIG_C_FOLDER_CATEGORY G_MIG_C_AUTHOR G_MIG_C_COMMENT G_MIG_C_REP_CUID G_MIG WID_CUID Description Explanation of why the error, warning or advisory occurred. The part of the document that generated the error, warning or advisory. A keyword that identifies the source of the error, warning or advisory. What the conversion process did to handle the problem that created the error, warning or advisory. The result further details the problem identified in the keyword. A workaround for the problem that created the error, warning or advisory. The user who ran the Report Conversion Tool. The repository folder containing the Desktop Intelligence document. The author of the Desktop Intelligence document. The comment the Report Conversion Tool. user entered when converting the document(s). Unique ID assigned to Desktop Intelligence report Unique ID assigned to Web Intelligence report Report Conversion Tool Guide 61

62 Audit table structure and data A Not converted documents Not converted documents In a case where the Report Conversion Tool cannot convert a document, it generates multiple lines in the log table: one line that begins with Error for the non-conversion, and one line for each object within each data provider that could not be converted. You can remove these additional lines to leave the Error lines only by running the following SQL script to clean the table: DELETE obj_g_migration WHERE g_mig_c_logentry > 0 AND g_mig_c_status = 'Not converted' AND EXISTS ( SELECT * FROM obj_g_migration2 mig1 WHERE mig1.g_mig_c_logdate = g_mig_c_logdate AND mig1.g_mig_c_docname = g_mig_c_docname AND mig1.g_mig_c_folder_category = g_mig_c_folder_category AND mig1.g_mig_c_logentry = 0 AND mig1.g_mig_c_status = 'Not converted' ) 62 Report Conversion Tool Guide

63 Business Objects Information Resources appendix

64 Business Objects Information Resources B Documentation and information services Documentation and information services Documentation Business Objects offers a full documentation set covering its products and their deployment. Additional support and services are also available to help maximize the return on your business intelligence investment. The following sections detail where to get Business Objects documentation and how to use the resources at Business Objects to meet your needs for technical support, education, and consulting. You can find answers to your questions on how to install, configure, deploy, and use Business Objects products from the documentation. What s in the documentation set? View or download the Business Objects Documentation Roadmap, available with the product documentation at documentation/. The Documentation Roadmap references all Business Objects guides and lets you see at a glance what information is available, from where, and in what format. Where is the documentation? You can access electronic documentation at any time from the product interface, the web, or from your product CD. Documentation from the products Online help and guides in Adobe PDF format are available from the product Help menus. Where only online help is provided, the online help file contains the entire contents of the PDF version of the guide. Documentation on the web The full electronic documentation set is available to customers on the web from support web site at: 64 Report Conversion Tool Guide

65 Business Objects Information Resources Customer support, consulting and training B Documentation on the product CD Look in the docs directory of your product CD for versions of guides in Adobe PDF format. Knowledge Exchange and Knowledge Base Our Knowledge Exchange is an open, online forum for Business Objects users to share business intelligence strategies, experiences, ideas, and opinions. It s a great way to find technical answers to your problems, rate the information you see, share thoughts with others, and receive specialized technical information. The Knowledge Base, accessible if you have a valid maintenance contract, is a regularly updated, searchable database containing technical articles and resolutions to customer cases. 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, and we will do our best to ensure that your suggestion is included in the next release of our documentation: [email protected]. Note: If your issue concerns a Business Objects product and not the documentation, please contact our Customer Support experts. For information about Customer Support visit: support/. Customer support, consulting and training A global network of Business Objects technology experts provides customer support, education, and consulting to ensure maximum business intelligence benefit to your business. How can we support you? Business Objects offers customer support plans to best suit the size and requirements of your deployment. We operate customer support centers in the following countries: USA Australia Report Conversion Tool Guide 65

66 Business Objects Information Resources B Customer support, consulting and training Canada United Kingdom Japan Online Customer Support The Business Objects Customer Support web site contains information about Customer Support programs and services. It also has links to a wide range of technical information including knowledge base articles, downloads, and support forums. 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. Expertise is available in relational and multidimensional databases, in connectivities, database design tools, customized embedding technology, and more. For more information, contact your local sales office, or contact us at: Looking for training options? From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style. Find more information on the Business Objects Education web site: 66 Report Conversion Tool Guide

67 Business Objects Information Resources Useful addresses at a glance B Useful addresses at a glance Address Business Objects product information Business Objects Documentation Roadmap documentation/ Product documentation support Business Objects Documentation mailbox [email protected] Online Customer Support support/ Business Objects Consulting Services services/consulting/ Business Objects Education Services services/training Content Information about the full range of Business Objects products. Overview of Business Objects documentation. Business Objects product documentation, including the Business Objects Documentation Roadmap. Send us feedback or questions about documentation. Information on Customer Support programs, as well as links to technical articles, downloads, and online forums. Information on how Business Objects can help maximize your business intelligence investment. Information on Business Objects training options and modules. Report Conversion Tool Guide 67

68 Business Objects Information Resources B Useful addresses at a glance 68 Report Conversion Tool Guide

69 Index Symbols #MULTIVALUE 57 and dimensions in block footers 57 and dimensions in block headers 57 and dimensions in sections 56 and non-aggregative measures 47 A Across Edge Display setting 30 ApplicationValue function 31 audit logs and Sybase databases 16 contents 60 creating 15 creating connection 15 setting up 15 Automatic refresh setting 28 Avoid Duplicate Row Aggregation property 46 B BlockNumber function 31 blocks Avoid Duplicate Row Aggregation 46 filtering 54 border styles 39 breaks folded 30 on multiple dimensions 30 on objects not in the block 30 value-based 30 Business Objects consulting services 66, 67 support services 66 training services 66, 67, 67 C calculation engine differences in behavior 45 cell border styles cell format border styles 32 cell format fill character 31 hide cell formula 31 cell formats converting styles 39 charts multiple groups 32 plot area 32 rotation, elevation, start angle 32 series color 32, 41 wall color 32 consultants, Business Objects 66 conversion compared to migration 45 defined 6 conversion status customizing with initialization file 7, 25 conversion step audit log data 15 describing workflows 9 Count() function 51 CountAll function 31 creating connection audit log 15 crosstabs Across Edge Display setting 30 CurrentPage function 31 customer support 66 D data providers OLAP 28 personal 28 stored procedure 28 Report Conversion Tool Guide 69

70 Index universe 28 DataProviderType function 31 date formats 31 Delete Trailing Blanks option 29 description Report Conversion Tool 6 Designer installing 8 detail objects 46, 46 dimensions in block headers and footers 57 in sections 56 placement of 56 Do Not Retrieve Data option 29 document properties Extend Merged Dimension Values 46 documentation feedback on 65 on product CD 65 on the web 64 roadmap 64 E education. See training empty values and Count() function 51 different definitions of 51 Enhanced Viewing setting 29 Extend merged dimension values property 47 extended dimension values 47 F feedback, on documentation 65 fill character 31 filters block 54 complex 29 global 29 global and block 39 indirect 55 on blocks 29 on formulas 29, 38 on measures 39 folded breaks 30 fonts 40 changing defaults 40 font mapping 33 free-hand SQL 34 Fully Converted reports 7 functions ApplicationValue 31 BlockNumber 31 Count 51 CountAll 31, 51 CurrentPage 31 DataProviderType 31 GetProfileNumber 31 GetProfileString 31 Hyperlink 31 Multicube 31 OLAPQueryDescription 31 PageInSection 31 Product 31 RunningSum 49 G GetProfileNumber function 31 GetProfileString function 31 grouped variables 37 H hidden objects 30 Hide Block formula 30 hide cell formula 31 Hide Section Footer formula 29 Hide Section Header formula 29, 29 Hyperlink function 31 I indirect filters 55 information resources 63, 64 initialization file editing 26 structure 26 installing client or server 8 70 Report Conversion Tool Guide

71 Index K keywords Report 53 M measures non-aggregative 44 migration compared to conversion 45 Multicube function 31 N non-aggregative measures 44, 47 Not Converted reports 7 O OBJ_G_MIGRATION audit table descriptions 60 OLAP data providers 28 OLAPQueryDescription function 31 OLE objects 29 Online Customer Support 66 options Delete Trailing Blanks 29 Do Not Retrieve Data 29 P page setup options 30 PageInSection function 31 Partly Converted reports 7 password protection 33 write 33 personal data providers 28 pictures 30 platforms Windows only 8 pre-requisites installing Designer 8 user settings 8 Product function 31 properties Avoid Duplicate Row Aggregation 46 Extend merged dimension values 47 protection password 33 Q query calculation 28 R relative dates 41 Report Conversion Tool overview 6 what is it 6 Report keyword 52, 53 reports accessing them for conversion 6 resources 63, 64 running functions and sort order 49 default reset behavior 49 RunningSum function 49 S scope of analysis 29 sections and dimensions 56 referencing data from 52 select and convert reports first step 9 Select Query Results operand 28 setting up audit log 15 sort order and running functions 49 sorts in queries 29 on blocks 32 stored procedure data providers 28 support customer 66 locations 65 technical 66 web site 66 Report Conversion Tool Guide 71

72 Index T technical support 66 training, on Business Objects products 66 U universe data providers 28 user objects 29 user settings pre-prequisites 8 V value-based breaks 30 variable description 32 variables grouped 37 VBA macros 30 view conversion results conversion workflow 9 W web customer support 66 getting documentation via 64 useful addresses 67 web sites support 66 training 66 write password Report Conversion Tool Guide