Business Intelligence with SAP Business Objects 4.3

Error WIS 00003 - Some pre-defined filters are no longer available in the universe. See your Business Objects administrator. One or more predefined filters are no longer available in the universe. Predefined filters are condition objects that are predefined WHERE clauses. You use these to restrict the data returned in a query. Solution  Remove the predefined filters from the query, and manually create the same condition in the query by using the appropriate operators and operands. Exception case: In order to correct this problem the designer has renamed one  object in the universe   and has replaced it with the previous original name. This action has not solved the problem: The correct fix is to delete the new object in the last universe version, copy the filter  object from the old universe containing the original filter and  paste it into the current version of the universe. See also: BUSINESS OBJECTS ERRORS LIST

Error WIS 00001 - Some objects are no longer available in the universe. See your Business Objects administrator One or more objects in a universe are no longer available to a document, because they have been deleted in the Universe. Solutions: If you have the old Universe backup ( containing the deleted objects nedeed)  you can publish it again otherwise delete the objects from the query that seem to be missing.  The available objects are listed on the Data tab. Rebuild the query without the obsolete objects. See also: BUSINESS OBJECTS ERRORS LIST

Universe Syntax Error This error message appears when special characters are used in object names, including: [ ] = & @ × $ % , ; ! ß £ ~ § μ + ' ( ) { } - There is no solution just: do not use special characters in object names. See also: BUSINESS OBJECTS ERRORS LIST

Transaction Log Based Data Replication Using Sybase Replication. This replication method is only recommended for customers that have been invited to use this technology during the RTC of the SAP HANA 1.0 product delivery. If you are not part of this RTC group, SAP recommends using Trigger-Based Data Replication Using SAP Landscape Transformation (SLT) Replicator because of the rich feature set this replication technology offers. The main components of this replication method are the Sybase Replication Agent which is part of the source system, SAP ERP, and the Sybase Replication Server which is to be implemented in SAP HANA. Replication Process in Detail The following image  details the data replication process and introduces the additional components of this replication method. Initial Load and Simultaneous Delta Replication The initial load of business data needs to be executed only one time to replicate the entire existing dataset from the source system t

The Extraction-Transformation-Load (ETL) based data replication uses SAP BusinessObjects Data Services (hereafter referred to as Data Services) to load the relevant business data from the source system, SAP ERP, and replicate it to the target, SAP In-Memory Database (IMDB). This method allows you to read the required business data on the level of the application layer. You deploy this method by defining data flows in Data Services and scheduling the replication jobs. Since this method uses batch processing, it allows also for data checks, transformations, synchronizing with additional data providers, and the merging of data streams. The data replication is operated by Data Services. Its main components are the Data Services Designer, where you model the data flow, and the Data Services Job Server for the execution of the replication jobs. An additional repository is used to store the meta data and the job definitions. Data Flow As for any replication scenario you have to def

The Trigger-Based Replication method uses the SAP Landscape Transformation (SLT) component to  pass data from the source system to the SAP In-Memory Database (IMDB) target system. Initial Load and Simultaneous Delta Replication The initial load of business data is initiated using the SAP In-Memory Computing Studio. The initial load message is sent from the SAP HANA system to the SLT system (based on SAP NetWeaver 7.02 with kernel 7.20) which in turn passes the initialization message to the ERP system. The ERP system begins by setting up database transaction log tables for each table to be replicated. After the transaction tables are completed, the SLT system begins a multi-threaded replication of data to the target system which allows high speed of data transfer to be achieved. The initial load of data can be executed whilst the source system is active. The system load that this process causes can be controlled by adjusting the number of worker threads performing the initial

LO 01003 - An error occurred when refreshing. Cause This error might be caused by the following reasons: 1. The report is corrupted. 2. Drawing Live Office object on unsupported areas, like Word Header or Footer, or Office 2007 PowerPoint Slide Master. 3. The server is not accessible. If not in the list, check the detail error. Action For cause: 1. Check from InfoView to make sure the document is valid. If yes, log-off and log-on BOE on Live Office Option dialog then try again, or re-start the Office application, then try again. 2. Do not drawing Live Office object on unsupported areas. 3. Fix the network connectivity or start up the server. If not in previous causes, use the error code in the detail to find the solution,or just follow the guide in the detail See also: BUSINESS OBJECTS ERRORS LIST

Translation Manager Exporting documents to the CMS After you translate the document, you need to select it for publishing and export it to the CMS.  You can publish it into as many languages as are ready . A built in document analyzer provides statistics on the percentage of the document that has translations so you can decide if you are ready to complete the publish step before exporting to the CMS. Universes can only be exported to the same file location. Web Intelligence documents can change locations. 1. Go to the Language Management view. 2. Click the value in the Ready to export to CMS column for the language or languages that you want to export to Yes. 3. Select Export to CMS from the File menu. A message appears to prompt you to save the document before exporting to the CMS. 4. Click Yes. The Export Universe/Webi Document dialog box appears. 5. Click Export to export the document and save it in the local file that is shown at the top of the dialog box. Click the

Installing and Using the SAP HANA ODBO Client for MS EXCEL Everyone  who intend to use Microsoft (MS) EXCEL as an end-user client for SAP HANA need to install the SAP HANA client on a host where MS EXCEL has been installed and is running. Prerequisites: You have downloaded the SAP HANA client software from SAP Service Marketplace . Procedure Install the SAP HANA ODBO driver on the host where MS EXCEL has been installed and is running. 1. Open a command prompt and call the SAP HANA client installation program by entering the following command: hdbinst -a client [ ] 2. Follow the instructions displayed by the installation tool. 3. Set the PATH environment variable to the installation path. For information on setting environment variables, see the documentation for your operating system. 4. Create a connection to the SAP HANA database: a. Create a connection to an external data source: Data connection Wizard Select t

There are three options to recover a deleted folder depending  on what kind of backup you have done: 1. backup of the CMS database and File Store. 2. You created recently a BIAR file. 3. You have a Development/Test environment where you have this folder. Let's see the  Solution in case you have a back up of the CMS database. Follow the steps to recover deleted folder and sub-folders: 1. Copy the CMS database from the backup to your database server and point the CMS ODBC system DSN to it. 2. Copy the backed up file store to a Temp directory. 3. Change the path of input and output file repository servers in the CMC, for each server, to the Temp file store directory. 4. You will now be able to find the reports. Copy those reports to the BusinessObjects server's local disk, or create a BIAR file using the Import Wizard. 5. Point the ODBC system DSN back to the original database, and also change the paths on input file repository and output file repository se

SAP HANA Persistence: In-Memory Data Is Regularly Saved to Disk  Data:  - SQL data and undo log information  - Additional HANA information, such as modeling data  - Kept in-memory to ensure maximum performance  - Write process is asynchronously Log:  - Information about data changes (redo log)  - Directly saved to persistent storage when transaction is committed  - Cyclical overwrite (only after backup) Savepoint:  - Changed data and undo log is written from memory to persistent storage  - Automatic  - At least every 5 minutes (customizable) For detail: SAP HANA - Data persistence

Using SAP BusinessObjects BI Clients for SAP HANA Creating the JDBC connection to the SAP In-Memory Database To set up the JDBC connection to the IMDB: 1. Copy the ngdbc.jar in the appropriate folder under …/dataAccess/ConnectionServer/jd bc/drivers/newdb If this directory structure does not exist, you need to create this directory structure under ../dataAc cess/connectionSrever/jdbc and then drop the jdbc jar file under this directory. 2. Launch the SAP BusinessObjects information design tool. 3. Create a new local project. 4. In this project, create a new Relational Connection. 5. Name it. 6. Select JDBC Drives as the data source. 7. Enter DB credentials and test. 8. Choose Finish. Note: for Explorer, you can also create a native connection from the IMDB to the Explorer application, by configuring the Explorer application settings in the SAP BusinessObjects Central Management Console (CMC). When this type of native connection is used for Explorer, a UNX file

After installing SAP HANA, you have to connect the components of your SAP HANA landscape so they can work together. You have to establish connectivity between the following components: 1. SAP HANA box to SAP ERP system 2. SAP HANA box to SAP HANA studio 3. SAP HANA box to end-user clients. If you are using the SAP BusinessObjects servers, which are not in the scope of SAP HANA, you also have to connect the following SAP BusinessObjects systems: 1. SAP HANA box to SAP BusinessObjects Enterprise (to use the SAP BusinessObjects BI clients) 2. SAP ERP system to SAP BusinessObjects Data Services (to use Data Services for data replication) See also: Create a Data Foundation (UNX) on a SAP HANA Universe on SAP HANA

Creating SAP BI URLs For Opening specific BI Documents or Reports SAP BusinessObjects Mobile for iOS 4.2.0 Pre-requisite Recipients of the SAP BI URLs (created using the format explained in this topic) have: - Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the URL. - The SAP Mobile for iOS app installed on their iPhone or iPad device. 1. Creating an SAP BI URL for opening a simple BI document (default view: first report, first page) in the app To give users access to a simple BI document on their iPad or iPhone devices, create an SAP BI URL with the following format: s apbi://OpenDoc/?ConnectionType=BOEConnection&connection_name=123&serv er_url=10.10.10.10:8080&cms=10.10.10.10&Type=webi&iDocID=AXtcyDP4u09Jn1_P9BSR9H0&reportPartKey=&reportPageNumber=0&reportIndex=&isInstance=N&prompt= • ConnectionType , connection_name, server_url and cms are the regular SAP BI URL paramete