Business Intelligence with SAP Business Objects 4.3

Business Objects Translation Manager (BO XI R3.x) Beginning from Business Objects Enterprise XI 3.0, SAP Business Objects provides a new support for multilingual content (Web Intelligence documents and universes) in order to allow the designer to create reports for a multilingual audience. The plus is that instead of having to create a report for each language, its content will be translated and the document will be displayed in the reader’s language, Translation Manager is the tool that provides a complete framework to support multilingual content in XI 3.x: • It proposes a simple graphical interface for easy and simple translations • It is fully integrated to the XI 3.x and supports all the supported CMS authentication modes as well as the offline mode. • It can collaborate with external translation tools by exporting and importing XLIFF (XML Localization Interchange File Format) files; the XML format for exchanging localization data. • It manages more than 100 locales. •

The web intelligence server memory is full. Please log off and try to connect later. If the problem persists, Contact your Business Objects Administrator. (Error_WIS_30280)(Error: INF) This is the official  resolution from service.sap.com/bosap-support:  BusinessObjects Note:  1277072 - Web Intelligence server memory full (Err:WIS:30280) error while refreshing the webintelligence reports  Symptom  Getting Web Intelligence server memory full (Err:WIS:30280) error while refreshing the webintelligence reports in Business Objects XIR2 infoview.  "Error: ' '"  The error message appears because the Web Intelligence server stresses the memory resources when processing many reports containing a large amount of data. Official Resolution   Log onto Central Management Console.  Click on Servers.  Click on Web_IntelligenceReportServer.  Click on Properties tab.  Reduce the Document Cache Duration to 20 minutes.  Reduce the Document Cache Scan Interval to

Creating and managing workbooks In SAP BO ANALYSIS you can insert SAP BEx Queries, query views and SAP Netweaver BW InfoProvider as data sources  in a workbook.  These data sources are stored in a SAP NetWeaver BW system. You can add multiple  crosstabs to worksheet or workbook.  The crosstabs can contain data from the same data source or from different sources. You can also use data sources that are stored in different systems in one workbook. To add a crosstab with data to a workbook, you select a data source in a SAP NetWeaver BW system. You need the appropriate authorizations for the platform you want to use (SAP NetWeaver BW or SAP BusinessObjects Business Intelligence), and the relevant SAP NetWeaver BW systems to insert a data source in a workbook. For more information, contact your IT administrator. You can insert a data source in a standard workbook or in a default workbook. If you use a default workbook, styles, formatting and the workbook settings t

SAP BusinessObjects  Analysis, Microsoft Office Edition It is new tool of BI 4 it is: Easy-to-use OLAP  analysis in Office Familiar and intuitive Microsoft   Office user experience Uncover deep insights with  powerful Excel-based analytical capabilities Bring  analyses into PowerPoint  presentations Leverage all your investments -  BW cubes and BEx queries, and BI platform SAP BusinessObjects Analysis, edition for Microsoft Office, is a Microsoft Office Add-In that allows multidimensional analysis of OLAP sources in Microsoft Excel, MS Excel workbook application design, and intuitive creation of BI presentations with MS PowerPoint. The Add-In is available for the following Microsoft Office versions: • Microsoft Office 2010 (Excel and PowerPoint) • Microsoft Office 2007 (Excel and PowerPoint) • Microsoft Office 2003 (Excel) In the edition for Microsoft Office, you can use SAP BEx Queries, query views and SAP Netweaver BW InfoProvider as data sources. The

Cause The maximum number of server connections allowed has been reached. Action Either raise the value of the maximum connections server parameter, or add another server instance. To modify the maximum connections value: 1.     Log on to BusinessObjects Enterprise Central Management Console (CMC). 2.     Click on Servers. 3.     Expand Server Categories, and click on Web Intelligence. 4.     Under Server name, double-click on WebIntelligenceProcessingServer. The Properties window appears. In Properties window, under Web Intelligence Processing Service, enter the value for Maximum Connections. Please note: Default value is 50 sessions. Valid range is between 5 and 65535 See also: BUSINESS OBJECTS ERRORS LIST

Environment BO XI 3.1 DataBase MS SQLSever 2008 While updating a Webi Report  occurred the following error: WIS 10901 Database error:[Microsoft][ODBC SQL Server Driver]Transaction (process ID 61) was deadlocked on lock communication buffer resources with another process and has chosen as the deadlock victim.  Solution Change Universe 'Connection pool  Mode' setting to: Disconnect after each transaction See also related posts: Error WIS 10901 - Database error occur BUSINESS OBJECTS ERRORS LIST

Version Management feature in the lifecycle management console The lifecycle management console tool enables you to manage versions of BI resources that exist in the SAP BusinessObjects Business Intelligence platform repository. It supports both Subversion and ClearCase version management systems. Let see  how to use the Version Management feature in the lifecycle management console tool. In order  to  create and/or manage different versions of an infoobject, follow the below directions: Log into the lifecycle management console - LCM In home page, select Version Management from the drop-down list. Enter the login credentials, and click Login, then the Version Management window appears. If you want to change the host system click on the 'Servers' icon and Login with different credentials. From the left panel of the "Version Management" window, select the folder to view the infoobjects whose versions you want to manage. Select the infoobjects and cl

Environment BusinessObjects XI 3.1 SP 4 Error :' Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' with BusinessObjects XI 3.1. Symptom Not able to schedule WebIntelligence reports. Reports fail with error:'Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' Resolution 1. From Central Configuration Manager, disable all the services and re-enable them. 2. Log into Central Management Console and go to the server area. 3. Go to the properties of Central Management Server, in command line parameters type -request timeout 3600000 (60 min). Please Note:  IdleSessionTimeout = Decimal 60000 (1 Min)  See also: BUSINESS OBJECTS ERRORS LIST

Dashboard Design (SWF)  to  Web Intelligence A Dashboard Design analytic used as a source document for Web Intelligence has to be configured with the FS Command connectivity . The parameters are then assembled in an OpenDocument URL by the Dashboard Builder framework. For more information about the OpenDocument syntax, please refer to Sap BO 4 Opendocument The connectivity between Dashboard Design and  WebI is very usefull  when summary data is displayed in the dashboard analytic  and  detailed data are available for a deep analysis in a WebI report. Let see how create a Content  Linking  setting Go to Dashboard Builder page: Create the  first   column in Dashboard Builder by importing the detailed Webi report that will be linked to the previous Dashboard Create the  second   column in Dashboard Builder by importing the Xcelsius Dashboard Define the content Linking Between the Xcelsius Dashboard ( named "Provider" in this example) and the W

Talking about Open document there are several features that changed in the new Business Intelligence platform 4.0. changed compared to XI R3.1 version. Let's see some hints: The default URL to the OpenDocument web application bundle has changed in SAP BusinessObjects Business Intelligence platform 4.0. New absolute OpenDocument links need to use the new default URL: http:// : /BOE/OpenDocument/opendoc/openDocument.jsp? & &...& Below you will see a lists of deprecated and obsolete OpenDocument parameters as of SAP BusinessObjects Obsolete parameters are no more supported. sIDType=GUID    ->  Use sIDType=CUID instead. sIDType=RUID     ->   Use sIDType=CUID  instead. sKind                    -> Use iDocID instead.          Specifies the SI_KIND property of the target                                                                        Desktop Intelligence document. sPath                              sPath does not support the use of lo

Life Office purpose To use Live Office to access corporate data,  you must connect to the SAP BusinessObjects Business Intelligence platform repository where documents are stored. When you attempt to search for, add, view, modify, or publish Live Office objects from a Microsoft Office application, if you are not already logged on to the BI platform, you are prompted to log on. You can configure Live Office to connect to SAP BusinessObjects Business Intelligence platform automatically each time Microsoft Office Excel, PowerPoint, Outlook, or Word is loaded. Live Office supports Single Sign-on (SSO) to the BI platform. If SSO is enabled, when users request report data, Live Office uses their SAP BusinessObjects Business Intelligence platform logon credentials to access the data source rather than requiring another logon. Live Office object types Crystal Reports ->  Fields: Yes   Report Parts: Yes Web Intelligence ->  Fields:  Not applicable  Parts: Yes U

In the Lifecycle Management Console, the new Dashboard Objects allows to check relashionship with universe query, dependences on QaaWS and universe objects in QaaWS connections, and/or dependences on WebIntelligence reports, Crystal reports and Universe objects with Life Office Connections. All the dependent objects can be promoted together. See also: Lifecycle Management Console LCM Managing infoobject versions How to import or export with lifecycle from cmd line

Binding chart to the query objects The great  new feature in SAP BO Dashboards allows to bind every single component of the dashboard  (charts, gauge and so on) directly to the query on the universe, this operation avoids to import values on the sheet in order to map    the component. Please note that when data is directly bound to a chart or other component this object will not display data in Design mode so you need to preview or publish the dashboard in order to view data. New components for Universe Connectivity: Query prompt selector  enables users to select one or more values for the prompt accordfing the operator used in the query. Please note that when a prompt selector is dragged to the canvass automaticcally it is added to the dahsboard. Query refresh button this allows users to refresh  data directly on demand in the dashboard   In SAP BO Dashboards 4.0 is now possible to  apply a   dynamic regional date, time, currency and numb

SAP BO DASHBOARDS 4.0   Servers In SAP Business Objects BI 4, BO Dashboard has been integrating in CMC management (auditing and monitoring included) as concerns the management of two new servers: DashboardDesignCacheServer DashboardDesignProcessingServer which support better performance and scalabilty. the first server provides data caching and sharing while the second manages query processes requests A great new feature of SAP BO Dashboard 4.0 is provided by the direct connection to a Universe trough a Query panel , the user interface is like WebI one so objects like dimensions and misures can be selected directly, besides you can apply filters,  sorts, prompts and you can preview the query data. The query  browser panel enables the dashboard designer to manage query on the universe, displaying the summary of result obejects, prompts and filters for each query launched providing in this way a quick access to tool to create, edit and refresh queries.

SAP BusinessObjects Dashboards 4.0 Supported Excel functions The SAP BO  Dashboards 4.0   supports the following Excel functions: A ABS ACOS ACOSH ADDRESS AND ASIN ASINH ASSIGN ATAN ATAN2 ATANH AVEDEV AVERAGE AVERAGEA AVERAGEIF B BETADIST C CEILING CHAR CHOOSE COLUMNS COMBIN CONCATENATE CORREL COS COSH COUNTIF Note: If used with large data sets, this function could affect performance. COUNT COUNTA COVAR D DATE DATEVALUE DAVERAGE DAY DAYS360 DB DCOUNT DCOUNTA DDB DEGREES DEVSQ DGET DIVIDE DMAX DMIN DOLLAR DPRODUCT DSTDEV DSSTDEVP DSUM DVAR DVARP E EDATE EFFECT EOMONTH EVEN EXACT EXP EXPONDIST F FACT FACTDOUBLE FALSE FIND FISHER FISHERINV FIXED FLOOR FORECAST FV G G GE GEOMEAN GT H H HLOOKUP  Note: If used with large data sets, this function could affect performance. HOUR HARMEAN I I IF INDEX INT INTERCEPT IPMT IRR ISBLANK ISERR ISERROR ISEVEN ISLOGICAL ISNA ISNONT

How to prepare Excel spreadsheets Before you import an Excel spreadsheet, make sure the spreadsheet provides a good structure for achieving the best performance for models. Consider the following guidelines: - Use only supported Excel functions For a list of supported Excel functions, see Supported Excel functions . - Use these Excel functions with small data sets only The following Excel functions are supported in Dashboard Design and Presentation Design, but can affect the model's performance if used with larger data sets (over 100 rows): • SUMIF • COUNTIF • HLOOKUP • VLOOKUP Note: If you must access larger data sets, have the server or database perform the aggregation on the server side. - Organize your data in a logical fashion To make your spreadsheet easier to understand, lay out your data in a logical fashion. Group related items together and use colors, labels, and borders to describe the structure and function of cells. - Use colors

Environment: BO XI R3.x After a migration from  BO  6.5 After creating  new users to wich have been given Deski rights to access to few universes in order to create reports. When they log in into Deski they see the universes but cannot open them from the query panel because an error occurs:  " Cannot load linked universes (UNV0011)". It looks like the Universe to which has been given access to has been linked to another Universe. Solution: Logon on CMC as    Administrator and give to universe which gave error  the same rights to the linked Universe in this way you can solve the above error. Hope this helps. See also: BUSINESS OBJECTS ERRORS LIST

Environments:   BOE XI R 3.1 + FP1  BOE XI R 2 + SP3 In order to solve the problem: 'Failed to import document. (DX0005)' or Cannot open document (Error: INF))  that occurs when viewing Deski reports through InfoView   the resolution was to grant the Everyone group the following rights under Applications -> Desktop Intelligence: - Log on to Deski and view this object in the CMC - Copy to Clipboard - Retrieve Documents - Refresh List of Values - Deski report interaction - Deski document interaction - Refresh Deski document - Refresh list of Categories Hopes this Help! See also: BUSINESS OBJECTS ERRORS LIST

Sizing the RAM needed Sizing an SAP HANA system is mainly based on the amount of data to be loaded into the SAP HANA database, because this determines the amount of main memory (or RAM) needed in an SAP HANA system. To size the RAM, the following steps have to be performed: 1. Determine the information that has to be transferred (either by replication or extraction) to the SAP HANA database. Note that typically customers will only select a sub-set of information from their ERP or CRM database, so this has to be done at the table level. The sizing methodology is based on uncompressed source data size, so in case compression is used in the source database, this has to be taken into account as well. The information required for this step can be acquired with database tools. SAP Note 1514966 contains a script supporting this process for several database systems, for example, DB2 LUW and Oracle. The current size of all the tables (without DB indexes) storing the required information

T-shirt sizes for SAP HANA SAP defined so-called T-shirt sizes for SAP HANA to both simplify the sizing and to limit the number of hardware configurations to support, thus reducing complexity. SAP’s hardware partners provide configurations for SAP HANA according to one or more of these T-shirt sizes. In addition to the T-shirt sizes listed in Table, you might come across the T-shirt size XL, which denotes a scale-out configuration for SAP HANA. The T-shirt sizes S+ and M+ denote upgradable versions of the S and M sizes: S+ delivers capacity equivalent to S, but the hardware is upgradable to an M size. M+ delivers capacity equivalent to M, but the hardware is upgradable to an L size. These T-shirt sizes are used when relevant growth of the data size is expected. For information about RAM sizing : Sizing the RAM for SAP HANA

SAP HANA database The heart of the SAP HANA database is the relational database engines. There are two engines within the SAP HANA database: - The column-based store, storing relational data in columns, optimized holding tables with huge amounts of data, which are aggregated and used in analytical operations. - The row-based store, storing relational data in rows, as traditional database systems do. This row store is more optimized for write operation and has a lower compression rate, and query performance is much lower compared to the column-based store. The engine used to store data can be selected on a per-table basis at the time of creation of a table. Tables in the row-store are loaded at startup time, whereas tables in the column-store can be either loaded at startup or on demand, during normal operation of the SAP HANA database. Both engines share a common persistency layer, which provides data persistency consistent across both engines. There is page manag

When talking about SAP HANA , these terms are used: SAP In-Memory Appliance (SAP HANA) SAP HANA is a flexible, data source agnostic appliance that allows you to analyze large volumes of data in real time, without the need to materialize aggregations. It is a combination of hardware and software, and it is delivered as an optimized appliance in  cooperation with SAP’s hardware partners for SAP HANA. SAP in-memory database , also referred to as the SAP HANA database The SAP in-memory database is a hybrid in-memory database that combines row-based, column-based, and object-based database technology, optimized to exploit the parallel processing capabilities of current hardware. It is the heart of SAP offerings like SAP HANA. For more detailed information see Sap Hana Database SAP HANA architecture See Also: In memory key concepts SAP HANA - Data persistence Sap Hana introduction SAP HANA - Additional Components