Posts

SAP HANA variable creation example

Image
Analytical view with parameter example We will use a simple analytical view as an example which will guide us for the rest of the document. The analytical view has been built from tables coming from a DWH sample schema. The screenshots of the view and of the variable and parameters management have been realized with the HANA Studio release 1.0.25 The Customers attribute view contains information about customers of the company. The view also contains the last name, the customer country, city and education as attributes available at query time. The Customer_id is used as the key attribute for the join with the fact table. This view is defined on top of the Customer table. The Products attribute view contains information about products. Will be presented only the product name and brand as attributes. Product_ID is the key attribute. The fact table used here is the Sales_2006 table. There is the join between the Product_Id and the Customer_id with the attribute views and we e

SAP HANA variables and parameters

Let's see SAP HANA basic information on variables and parameters which for could be  relevant for BI designers. In SAP HANA it is possible to define the results of a query on an information model at runtime by passing values to the model. There are two kinds of input values which can be passed to a model: variables and parameters. Both variables and parameters will appear as prompts for the user running the query (or will be automatically filled in by the application calling the HANA information model). HANA variables HANA variables are used to filter the content of an information model. They don ‟ t impact the execution workflow of the information model and are applied to a query to filter out some values. Variables can be used to filter attributes. As an example, a variable can be used to filter a result to a specific country or a specific customer. In SQL, variables are applied in the WHERE clause of the query. HANA parameters Parameters are used to

Universe on SAP HANA

Choosing between creating HANA information models and universes Client tool Requires a Universe Access HANA data via: SBO Analysis Office             No                       an information model SBO Explorer (*) Microsoft Excel (PivotTable) SBO Web Intelligence Yes                       a universe built on tables or information models SBO Dashboards SBO Crystal Reports for Enterprise (*) Explorer could also be connected to universes When you have to begin a new business intelligence project on HANA, the first question to ask yourself is whether you want to (or need to) create information models or universes. At the moment  your choice mainly depends on the client tool that you want to use to access HANA. When you create information models you benefit from: -Availability to Analysis, Explorer, Excel, reusability in Universes -SQL Script, L, R languages for programmatic calculation view -Modeling in HANA Studio When

ERROR WIS 30567 - Could not save document to the repository

Could not save document to the repository  (WIS 30567) Environment : BusinessObjects XI3.1 SP3; Windows Server 2003 SP2 Errors erased when trying to save Web Intelligence documents "Could not save the document to the repository for the following reason: [repo_proxy 30] InfoStore::ObjectExport::commit - (Helpers::InfoStore::ObjectExport::commit) File Repository Server error: Could not save the file .wid to the File Repository Server. File already exists. (hr=#0x80042a4a)(Error #-2147210678 (WIS 30567)" This error tells that when report was being saved into Input FRS, another report with the same ID was found there and the product couldn't overwrite it. So possible reasons are: you have no rights to overwrite docs in the BOE there are OS issues with restrictios on IFRS Drive space issues Beside, make sure the following servers are up and running and also check your rights on saving the object in BOE: Web Intelligence Report Server Input Report

SAP HANA REPLICATION DATA

Image
SAP In-Memory reporting and analyzing of business data requires the replication of the data from a source system to SAP In-Memory Database (IMDB). Let see an overview of the possible replication methods that are available for SAP In-Memory Appliance (SAP HANA 1.0) and its the application fields and the main components required for each method. There are three methods available for performing the data replication.  The main components involved in all replication scenarios are: • SAP HANA, consisting of the IMDB and SAP In-Memory Computing Studio, which is used to administer the appliance. User interfaces, such as SAP BusinessObjects Dashboards or Web Intelligence or Visual  Intelligence. • Source system, such as SAP ERP • Software components supporting the data replication The software components that support different methods of data replication are described in the following  three replication scenarios. There are three alternative methods for data repli

BUSINESS OBJECTS ERRORS LIST

Hello Everybody, would you help to collect more frequent BO Errors,  better if indicating BO version? If you want you can also write down your personal fix or standard solution. This could by useful for somebody. Thanks in advance for co-operating! Best regards Giuseppe SAP BI 4 - Scheduling reports error - source file error. [Invalid argument]: [CrystalEnterprise.DiskUnmanaged] wij-20002 error webi rich client Internal error Error RFC 00101 - No server was available to process the request FWM 00001 Transport error: Communication failure. Error WIS 30272 - Max character file size limit exceeded Error WIS 00509 - Universe data connection could not be found Error RWI 00323 - Cannot retrieve the document with the passed obsolete token Error RWI 00239 - Connection failed. The server has reached the maximum number of simultaneous connections Error RWI 00239 - The maximum number of server connections allowed has been reached Error RWI 00322 - An error occurred whi

Strategy Builder in Performance Manager

Strategy Builder in Performance Manager Environment: Business Objects XI R 3.1 SP3 Strategy Builder is useful because: • It allows companies to set and manage strategies for using enterprise information. • It ties information usage to business roles and objectives. • It optimizes information usage around the extended enterprise. A key element of Strategy Builder is its awareness of the corporate organization structure.  It takes into account the roles that are in the company, and ensures that the appropriate people are getting the appropriate information. The Strategy Builder has four tabs: • Home • Strategy • Catalog • Organization When you open Strategy Builder, the Strategy Builder schema appears on the main panel. Click objects in the map to see the different areas of Strategy Builder. The "Strategy" tab in Performance Manager Strategy Builder offers an overall perspective on the strategy hierarchy tree defined within Performance Manager. Navigate dir

SAP VISUAL INTELLIGENCE FEATURES

VISUAL INTELLIGENCE FEATURES AND EVOLUTION A new BI general need  about a fast data visualization that enables  interactive data visualization and self consumption is now covered by SAP with SAP VISUAL INTELLIGENCE. Through  Visual Intelligence SAP aims to answer the growing demand for self-service data visualization in order to realize an analytic dashboard tool. SAP Visual Intelligence was originally released during the May 2012 SAPPHIRE NOW event, and a new version, was released as Feature Pack 3 for BI BusinessObjects 4 . Concerning  power and complexity, SAP Visual Intelligence is positionated between the dashboards such as SAP BusinessObjects Dashboards (a.k.a Xcelsius) and SAP Zen, and the self-service web and mobile tools of SAP BusinessObjects Explorer. SAP Visual Intelligence is part of the SAP BusinessObjects Explorer family, but while BusinessObjects Explorer allows for data exploration and visualization via a web service or through a mobile app, SAP Visual Intelli

Excel Best Practices in Xcelsius Dashboard

At designing your dashboard time in BO Dashborards or Xcelsius follow the best practices concerning  Microsoft Excel. Is suggest to avoid: - Array calculations as they can dramatically affect performance: 1. SUM 2. COUNT 3. SUMIF 4. COUNTIF 5. INDEX 6. MATCH 7. HLOOKUP 8. VLOOKUP 9. and similar - Repeating logic:     This example will run the SUM twice : IF(SUM(A1:A10),   , SUM(A1:A10))  Any calculations: They add overhead when loading or interacting with the dashboard They increase the time it takes to generate the flash file when you export or preview Is better to:  - Hard code values wherever possible instead of using formulas - Define calculations on the server side where possible - Use server side sorting to order your data and make the results easier to compare - Use server side ranking to limit the number or rows returned - Link to a report for detailed drill down - Use a selector with filtered rows instead of Excel lookups - Us

Variables that influence BO Dashboard Performances

Variables that impact on Dashboard  Load Time In order of importance: 1. Queries or connections that are set to Refresh Before Components Are Loaded.           This is the default setting for a query.            If you have any queries or connections set to refresh before components are              loaded the             Initializing message phase stays up until they have all completed. 2. Excel cells 3. Excel calculations 4. Components 5. Bindings from components to Excel (also size of ranges) 6. Dashboard file size Please Note: Default  maximum number or rows you can refer to in a formula or in a binding is  512  rows. You can  change this in  File  >  Preferences  >  Excel Options  (max recommended is  2000  rows) but this may affect the performance of your dashboard. See Also: SAP BusinessObjects Dashboards 4.0 - Spreadsheets

Using Microsoft Excel in BO Dashboards

Benefits from using Microsoft Excel in designing SAP BO Dashboards 4.0 Should you continue to use Microsoft Excel also in BO Dashoboard 4.0? Apart from Microsoft Excel having a wide reach among business users and being easy to use, there are three main benefits that Microsoft Excel provides when embedded inside the Dashboards designer: A Data Model. You can enter highly aggregated data directly into the spreadsheet and visualize it, so there is no need for a database. You can also pull in highly aggregated data from external sources, including SAP Business Warehouse (BW), SAP BusinessObjects Business Intelligence (BI) universes, XML and simple Web services. A Calculation Engine. In addition to Microsoft Excel having a very familiar and flexible formula language, it also provides a calculation engine. An Eventing Model. When a cell changes, we get a “data change” event. This is a very simple model, but we leverage it for more than just calculations. You can either start wi

SAP Visual Intelligence

Image
The new Visual BI Interface Tap into your data - big and small - and discover answers with SAP Visual Intelligence software.  Fast data manipulation and engaging visualizations allow you to combine and analyze data from a variety of enterprise and personal sources and quickly discover unique insight – no scripts, predefined queries or reports required. With SAP Visual Intelligence, you can: Deliver faster time to insight in a repeatable, self-service way Maximize business knowledge with a combination of big picture insights and granular details Accelerate decision making with immediate, fact-based answers to complex business questions Increase self-service data usage without adding to your IT department's workload Visualize any amount of data in real time – with SAP HANA For detailed information visit the official SAP site: SAP Visual Intelligence See Also: Using SAP Visual Intelligence Connect SAP Visual Intelligence to data sources

Error DMA0005 - Export failed

Err DMA0005 - Export failed! Environment: BO XI R 3.1 Cause This error message appears as the result of a failure after you have selected one of the following file export options: • Export to local file format - In the case of an attempted export to a dBase or Excel file, there has been a general export failure that was possibly caused by unavailable target files, a Microsoft DAO internal error (such as an absent ISAM driver), or not enough disk space. In the case of an attempted export to a text file, there has been a general export failure that was possibly caused by unavailable target files or not enough free disk space. Copy to DDE - In the case of an attempted export to DDE (the Windows Clipboard), there has been a general export failure that was most likely caused by insufficient memory. • Export to RDBMS - In the case of an attempted export through a BusinessObjects connection, there has been a general export failure possibly caused by an improper middleware confi

Translation Manager Substitution mechanism

The substitution mechanism (also known as the fallback) provides the metadata information about the strings translated status. You can define: • The languages in the document definition. The languages must first be set to "YES" for the "Ready to Export to CMS" attribute. • The substitution language for the document. A document has one substitution language identified as fallback language . You define or edit one substitution language in the Translation Manager. This doesn't impact any workflow changes on the consumption side (InfoView or Web Intelligence Rich Client). As an example , a document is translated in English, French and Italian. The substitution language is English. If you want to view its Spanish version even though it is not translated you will view its substitution language, i.e. English. See Also: How to use Translation Manager Translation Manager Translation Manager Exporting documents